Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4e6915d0086a9ea38c5ca19a533581b838f678ea30da8c9c22e97802786fdec

Tx prefix hash: 201b4baeee07b22b851cd5cb271e79ea9f1b0bd225cf378e16ba6e0735653f79
Tx public key: b82b94644e50bffc9f8c1211472eb4deaa55af37fe8b4ba4c77fa39681448aa1
Timestamp: 1633157082 Timestamp [UCT]: 2021-10-02 06:44:42 Age [y:d:h:m:s]: 03:125:03:58:51
Block: 345001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 866145 RingCT/type: yes/0
Extra: 01b82b94644e50bffc9f8c1211472eb4deaa55af37fe8b4ba4c77fa39681448aa10211000000028d0de867000000000000000000

1 output(s) for total of 44.143716871000 dcy

stealth address amount amount idx
00: fab84dab331135af1fcbadc943c95a2367bf49bbd18b955ecf3ab53532c00d5b 44.143716871000 707749 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": 345011, "vin": [ { "gen": { "height": 345001 } } ], "vout": [ { "amount": 44143716871, "target": { "key": "fab84dab331135af1fcbadc943c95a2367bf49bbd18b955ecf3ab53532c00d5b" } } ], "extra": [ 1, 184, 43, 148, 100, 78, 80, 191, 252, 159, 140, 18, 17, 71, 46, 180, 222, 170, 85, 175, 55, 254, 139, 75, 164, 199, 127, 163, 150, 129, 68, 138, 161, 2, 17, 0, 0, 0, 2, 141, 13, 232, 103, 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