Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6628fa5ec0a8bdb9d37e346903405baf2e4e713e1dba04b62fb16ec2915b3801

Tx prefix hash: a4ae2c3f068c8684c8de74ec2fc13db9263f65fa796973b105e96af262e7f8ee
Tx public key: 2c5a79ed9e49ab3f87dd7770842048e8536fee7dc47cb99662fab758237573ae
Timestamp: 1647066336 Timestamp [UCT]: 2022-03-12 06:25:36 Age [y:d:h:m:s]: 02:286:18:25:02
Block: 456640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724483 RingCT/type: yes/0
Extra: 012c5a79ed9e49ab3f87dd7770842048e8536fee7dc47cb99662fab758237573ae02110000000b2e6b1fd5000000000000000000

1 output(s) for total of 18.837149667000 dcy

stealth address amount amount idx
00: 18d8855d9d4351b5ad0c7a90af857c863d1891232020cad683482774f8bb3db9 18.837149667000 872737 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": 456650, "vin": [ { "gen": { "height": 456640 } } ], "vout": [ { "amount": 18837149667, "target": { "key": "18d8855d9d4351b5ad0c7a90af857c863d1891232020cad683482774f8bb3db9" } } ], "extra": [ 1, 44, 90, 121, 237, 158, 73, 171, 63, 135, 221, 119, 112, 132, 32, 72, 232, 83, 111, 238, 125, 196, 124, 185, 150, 98, 250, 183, 88, 35, 117, 115, 174, 2, 17, 0, 0, 0, 11, 46, 107, 31, 213, 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