Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3233dc00bd1715a4fde8268c04c535efc861090c2701e21d43d10b6698ad24c

Tx prefix hash: a308a5e3feb2a19eeb8213082b99eedede39d8802858989b02e22ab720e48d28
Tx public key: a61c0958f2008c9b3eb437114bfc9b9d200e11e5a2aee12fecbe0b0d5572a2b3
Timestamp: 1704572033 Timestamp [UCT]: 2024-01-06 20:13:53 Age [y:d:h:m:s]: 01:079:16:26:27
Block: 929630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318050 RingCT/type: yes/0
Extra: 01a61c0958f2008c9b3eb437114bfc9b9d200e11e5a2aee12fecbe0b0d5572a2b302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 559b39cdd41297c6e1a8403f54ea4c42c3c3002dc3143632f7e76393e05d1a20 0.600000000000 1387506 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": 929640, "vin": [ { "gen": { "height": 929630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "559b39cdd41297c6e1a8403f54ea4c42c3c3002dc3143632f7e76393e05d1a20" } } ], "extra": [ 1, 166, 28, 9, 88, 242, 0, 140, 155, 62, 180, 55, 17, 75, 252, 155, 157, 32, 14, 17, 229, 162, 174, 225, 47, 236, 190, 11, 13, 85, 114, 162, 179, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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