Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5d872fe0dd6984775b7790b65fd3db9e7a07343defd48646f1eec8bd2a4426d

Tx prefix hash: c4db6a3541b1627f9bc75821fcc936cca45a92b9b287abd1c1be904506952439
Tx public key: b73512c02fb131f9d2c66bb12da9e77d0311d4784f4b40eef8985c5c5caf0e4d
Timestamp: 1583236736 Timestamp [UCT]: 2020-03-03 11:58:56 Age [y:d:h:m:s]: 04:297:13:59:12
Block: 75452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107116 RingCT/type: yes/0
Extra: 01b73512c02fb131f9d2c66bb12da9e77d0311d4784f4b40eef8985c5c5caf0e4d0211000000bdc71d3ff9000000000000000000

1 output(s) for total of 345.141354377000 dcy

stealth address amount amount idx
00: 4dc9df28c36583331d5074e1f1b405e9efdd38afceef830512ae53399992409b 345.141354377000 139393 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": 75462, "vin": [ { "gen": { "height": 75452 } } ], "vout": [ { "amount": 345141354377, "target": { "key": "4dc9df28c36583331d5074e1f1b405e9efdd38afceef830512ae53399992409b" } } ], "extra": [ 1, 183, 53, 18, 192, 47, 177, 49, 249, 210, 198, 107, 177, 45, 169, 231, 125, 3, 17, 212, 120, 79, 75, 64, 238, 248, 152, 92, 92, 92, 175, 14, 77, 2, 17, 0, 0, 0, 189, 199, 29, 63, 249, 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