Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a948e8884ab9a91bfc47f243b46a56d5bc4b3d0e4df3c5b8b961fc62bad84784

Tx prefix hash: ec950cf8afeed484650ba14334c6d65e16947e3a74994740c3fbdfefc3f6dfa1
Tx public key: 08ab32ab540f44c3550ca5d218100af1e17397e4fd8c90e765fc0feae1a5791e
Timestamp: 1706997463 Timestamp [UCT]: 2024-02-03 21:57:43 Age [y:d:h:m:s]: 01:084:14:45:44
Block: 949742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321562 RingCT/type: yes/0
Extra: 0108ab32ab540f44c3550ca5d218100af1e17397e4fd8c90e765fc0feae1a5791e02110000000181d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11e660a3b0d20c6f01d59de40e009f1718b0858cdb20e28422e9f3fd89e06507 0.600000000000 1408274 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": 949752, "vin": [ { "gen": { "height": 949742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11e660a3b0d20c6f01d59de40e009f1718b0858cdb20e28422e9f3fd89e06507" } } ], "extra": [ 1, 8, 171, 50, 171, 84, 15, 68, 195, 85, 12, 165, 210, 24, 16, 10, 241, 225, 115, 151, 228, 253, 140, 144, 231, 101, 252, 15, 234, 225, 165, 121, 30, 2, 17, 0, 0, 0, 1, 129, 215, 29, 85, 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