Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0286d3f0bc5bb6605ba6de39914adb639a0233721942f9c132a6eda1646724b

Tx prefix hash: 339a0dc6d4979b8925f76d40236064bc5d3184caf67adc700c38d19e0d7cb6c2
Tx public key: 1ee09baa3bf1e947473c8b1782763a067e848e73b7a28d8ba9245d80f54b0525
Timestamp: 1608891384 Timestamp [UCT]: 2020-12-25 10:16:24 Age [y:d:h:m:s]: 04:313:05:27:47
Block: 169079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1234359 RingCT/type: yes/0
Extra: 011ee09baa3bf1e947473c8b1782763a067e848e73b7a28d8ba9245d80f54b052502110000070e57f0ba47000000000000000000

1 output(s) for total of 168.961113659000 dcy

stealth address amount amount idx
00: 6fbcdeb80e02204ceeadb8b83ad6adc88c110286c95645ec7da113d59f6898f4 168.961113659000 314898 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": 169089, "vin": [ { "gen": { "height": 169079 } } ], "vout": [ { "amount": 168961113659, "target": { "key": "6fbcdeb80e02204ceeadb8b83ad6adc88c110286c95645ec7da113d59f6898f4" } } ], "extra": [ 1, 30, 224, 155, 170, 59, 241, 233, 71, 71, 60, 139, 23, 130, 118, 58, 6, 126, 132, 142, 115, 183, 162, 141, 139, 169, 36, 93, 128, 245, 75, 5, 37, 2, 17, 0, 0, 7, 14, 87, 240, 186, 71, 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