Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20a873c9db1600f6fa1820645576189cfda896efe4e5c0e3c56228f553b64d6b

Tx prefix hash: 87ef9d0043f4743c3437d20ce6dcc9e0371582b21ce7286f21cd779010bee574
Tx public key: 7c5286aa48fa5af1b03ab86b54f1ab0ee5300d839528285835be1c7e953daf49
Timestamp: 1717756982 Timestamp [UCT]: 2024-06-07 10:43:02 Age [y:d:h:m:s]: 01:076:16:11:51
Block: 1038967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313438 RingCT/type: yes/0
Extra: 017c5286aa48fa5af1b03ab86b54f1ab0ee5300d839528285835be1c7e953daf490211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a642867722ca5a6ecc8d8df4f01bc48f7f4b21e411d2e1a7aa7a9553573cba2d 0.600000000000 1507544 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": 1038977, "vin": [ { "gen": { "height": 1038967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a642867722ca5a6ecc8d8df4f01bc48f7f4b21e411d2e1a7aa7a9553573cba2d" } } ], "extra": [ 1, 124, 82, 134, 170, 72, 250, 90, 241, 176, 58, 184, 107, 84, 241, 171, 14, 229, 48, 13, 131, 149, 40, 40, 88, 53, 190, 28, 126, 149, 61, 175, 73, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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