Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e2a48c64a97ee19d836fb5a718fc70d7336a748527033e31f6b1d16f73ec13f

Tx prefix hash: 695cc7aed6fa608c6c9a5bd944f8a698ab4bb4874dc09f85b6e5a4bddb3d4de9
Tx public key: b948518af3b8fae015d9ebd718878c9e21feb091b51244b8c2a2c2a353fad0ee
Timestamp: 1582363557 Timestamp [UCT]: 2020-02-22 09:25:57 Age [y:d:h:m:s]: 05:065:10:45:57
Block: 70155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1199936 RingCT/type: yes/0
Extra: 01b948518af3b8fae015d9ebd718878c9e21feb091b51244b8c2a2c2a353fad0ee02110000000ad81c26c0000000000000000000

1 output(s) for total of 359.375251303000 dcy

stealth address amount amount idx
00: 4236c4e9a00e88bde90113a324083ee8276138837d9215dd3030f2f4260e1aff 359.375251303000 129511 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": 70165, "vin": [ { "gen": { "height": 70155 } } ], "vout": [ { "amount": 359375251303, "target": { "key": "4236c4e9a00e88bde90113a324083ee8276138837d9215dd3030f2f4260e1aff" } } ], "extra": [ 1, 185, 72, 81, 138, 243, 184, 250, 224, 21, 217, 235, 215, 24, 135, 140, 158, 33, 254, 176, 145, 181, 18, 68, 184, 194, 162, 194, 163, 83, 250, 208, 238, 2, 17, 0, 0, 0, 10, 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