Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f7f1881f2bba73ac4523cdf9efc637dd6c35e67d5c885a3809954eb1370ca23

Tx prefix hash: 34162b6a5749c2571e8ad8cac77bb9462b1aa356826f88a7ff324abba5d361fd
Tx public key: 5ac62f7bde3fd7e021cfb748cf8db6d3645e80933c5d1ce927d536134178ae9d
Timestamp: 1763455159 Timestamp [UCT]: 2025-11-18 08:39:19 Age [y:d:h:m:s]: 00:003:12:37:55
Block: 1414691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2523 RingCT/type: yes/0
Extra: 015ac62f7bde3fd7e021cfb748cf8db6d3645e80933c5d1ce927d536134178ae9d02110000000570609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13a5a104aa0c1daf9a22ade9540a38152e02023bfeb6da6f449bbdd160fd261a 0.600000000000 1903182 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": 1414701, "vin": [ { "gen": { "height": 1414691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13a5a104aa0c1daf9a22ade9540a38152e02023bfeb6da6f449bbdd160fd261a" } } ], "extra": [ 1, 90, 198, 47, 123, 222, 63, 215, 224, 33, 207, 183, 72, 207, 141, 182, 211, 100, 94, 128, 147, 60, 93, 28, 233, 39, 213, 54, 19, 65, 120, 174, 157, 2, 17, 0, 0, 0, 5, 112, 96, 157, 3, 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