Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cc1b2ea6ebfbfc0263e22c8dba1e2ce2b98d2c13cae0d56a2ef19bdf6d4d6ad

Tx prefix hash: 2a0b84c3d4a6bc57abd6e01994ed789d51bed45ddfe7ac190d8dabf15abfb2a3
Tx public key: 675d2dd5b3cee08584f7837dfc309ce1985cf96192354c202a8eba80726d0d58
Timestamp: 1582091065 Timestamp [UCT]: 2020-02-19 05:44:25 Age [y:d:h:m:s]: 04:281:18:02:24
Block: 67832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093905 RingCT/type: yes/0
Extra: 01675d2dd5b3cee08584f7837dfc309ce1985cf96192354c202a8eba80726d0d58021100000011d81c26c0000000000000000000

1 output(s) for total of 365.801289805000 dcy

stealth address amount amount idx
00: 3d12a431543ed5b5dc0f589ce33a35f6e6e7f83b6236f9c167523fac11a2f613 365.801289805000 124996 of 0

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": 67842, "vin": [ { "gen": { "height": 67832 } } ], "vout": [ { "amount": 365801289805, "target": { "key": "3d12a431543ed5b5dc0f589ce33a35f6e6e7f83b6236f9c167523fac11a2f613" } } ], "extra": [ 1, 103, 93, 45, 213, 179, 206, 224, 133, 132, 247, 131, 125, 252, 48, 156, 225, 152, 92, 249, 97, 146, 53, 76, 32, 42, 142, 186, 128, 114, 109, 13, 88, 2, 17, 0, 0, 0, 17, 216, 28, 38, 192, 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