Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c37a2bf491c1a32dec0c8c941be0ba0e450851772ae066ad45b77e9a404c2671

Tx prefix hash: 9ab3402bb795f1b7ecb8e81317823f1415f22668fd36c3c681d525cccead17ae
Tx public key: 8b75d9e5979051844355c23a478218d770d1cb6b799bfd75eba8d1d83bdb3011
Timestamp: 1734360093 Timestamp [UCT]: 2024-12-16 14:41:33 Age [y:d:h:m:s]: 00:093:07:24:18
Block: 1176515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66480 RingCT/type: yes/0
Extra: 018b75d9e5979051844355c23a478218d770d1cb6b799bfd75eba8d1d83bdb30110211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a03f7f1fa494e5cee86aa461fd4412cbf420c62d34b2e7a0470a60dbc0616c1f 0.600000000000 1662856 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": 1176525, "vin": [ { "gen": { "height": 1176515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a03f7f1fa494e5cee86aa461fd4412cbf420c62d34b2e7a0470a60dbc0616c1f" } } ], "extra": [ 1, 139, 117, 217, 229, 151, 144, 81, 132, 67, 85, 194, 58, 71, 130, 24, 215, 112, 209, 203, 107, 121, 155, 253, 117, 235, 168, 209, 216, 59, 219, 48, 17, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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