Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 40cbd4330c5c2911ccc4dd7a18c67d930ed0f1021cf6f08f57c77f16885bab0d

Tx prefix hash: 6a771c95637095c26ab1236da425f312bbcf44bebba85e7cbd7104e6474126ff
Tx public key: 770d4f1afc0f4651442bc017c6a8c6f340aa6f862d25b54b8e26609347c5a246
Timestamp: 1710115442 Timestamp [UCT]: 2024-03-11 00:04:02 Age [y:d:h:m:s]: 01:063:03:16:17
Block: 975615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306132 RingCT/type: yes/0
Extra: 01770d4f1afc0f4651442bc017c6a8c6f340aa6f862d25b54b8e26609347c5a2460211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60bc1638c2ce5bfb80bd324fdc50345d84913a541bacfcdd4fac9731d427c796 0.600000000000 1435588 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 975625, "vin": [ { "gen": { "height": 975615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60bc1638c2ce5bfb80bd324fdc50345d84913a541bacfcdd4fac9731d427c796" } } ], "extra": [ 1, 119, 13, 79, 26, 252, 15, 70, 81, 68, 43, 192, 23, 198, 168, 198, 243, 64, 170, 111, 134, 45, 37, 181, 75, 142, 38, 96, 147, 71, 197, 162, 70, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8