Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b5ba3eeda9a662bb6687dfe1cd97f6421395a630bdedca922d84a48ae719fce

Tx prefix hash: b4c3d0a856f0ce7d70ca92e3f21f253d8f26b915229e33dde7d10ae39c9f123e
Tx public key: 789909052b400f0188c01c060432e9ffdc3c16a606b685825b5325acc38e8c46
Timestamp: 1719712938 Timestamp [UCT]: 2024-06-30 02:02:18 Age [y:d:h:m:s]: 00:336:13:45:00
Block: 1055167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240555 RingCT/type: yes/0
Extra: 01789909052b400f0188c01c060432e9ffdc3c16a606b685825b5325acc38e8c460211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40cdb06e3326bdf3afc7f92e214a6c8a0cdb0adc70242b57a95351759d2350b7 0.600000000000 1525560 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": 1055177, "vin": [ { "gen": { "height": 1055167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40cdb06e3326bdf3afc7f92e214a6c8a0cdb0adc70242b57a95351759d2350b7" } } ], "extra": [ 1, 120, 153, 9, 5, 43, 64, 15, 1, 136, 192, 28, 6, 4, 50, 233, 255, 220, 60, 22, 166, 6, 182, 133, 130, 91, 83, 37, 172, 195, 142, 140, 70, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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