Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c70731d608e42b7d446ab84d8de160871142409042604490ae66462164d7f46f

Tx prefix hash: 740c69322dfb4da82fd43851321e4066b98dfd2204f1aed50df4f7226ff3c423
Tx public key: d634c6b1f5d88c972c37a3894aeea8afe5470ea051757702d1ac6aea336a36d3
Timestamp: 1722403419 Timestamp [UCT]: 2024-07-31 05:23:39 Age [y:d:h:m:s]: 00:301:22:21:33
Block: 1077477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215742 RingCT/type: yes/0
Extra: 01d634c6b1f5d88c972c37a3894aeea8afe5470ea051757702d1ac6aea336a36d3021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ee3260645b43e5abef1c9cf9cf166f5a51808dd82ea392b695611d0708995c6 0.600000000000 1550026 of 15

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": 1077487, "vin": [ { "gen": { "height": 1077477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ee3260645b43e5abef1c9cf9cf166f5a51808dd82ea392b695611d0708995c6" } } ], "extra": [ 1, 214, 52, 198, 177, 245, 216, 140, 151, 44, 55, 163, 137, 74, 238, 168, 175, 229, 71, 14, 160, 81, 117, 119, 2, 209, 172, 106, 234, 51, 106, 54, 211, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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