Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b28890fd577760acbf7dc7681c4819d97e86fb2d283317875ae68b1c99ca31b

Tx prefix hash: a8c616d91a5b355b2d39c02fb4a1d30584ffe7d5b9bf7165d19a6f7c94c49ee2
Tx public key: 49afd6f72fefc2de587b2431fdbee8fa046489478d892487d5c726d31db458fc
Timestamp: 1717633939 Timestamp [UCT]: 2024-06-06 00:32:19 Age [y:d:h:m:s]: 00:270:20:36:25
Block: 1037941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193548 RingCT/type: yes/0
Extra: 0149afd6f72fefc2de587b2431fdbee8fa046489478d892487d5c726d31db458fc0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a98623375b560d229e5c03b46c4abc28aec7d34dd7c6a110a4cfb650b3782661 0.600000000000 1506498 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": 1037951, "vin": [ { "gen": { "height": 1037941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a98623375b560d229e5c03b46c4abc28aec7d34dd7c6a110a4cfb650b3782661" } } ], "extra": [ 1, 73, 175, 214, 247, 47, 239, 194, 222, 88, 123, 36, 49, 253, 190, 232, 250, 4, 100, 137, 71, 141, 137, 36, 135, 213, 199, 38, 211, 29, 180, 88, 252, 2, 17, 0, 0, 0, 6, 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