Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65b1e53a8c6fd71e1318cc46ff66b1934cf6434ff07dd2c6fa0a661e98bba3e2

Tx prefix hash: 8ba81cfb6728a8611601902f51e3c84c85178c99f8eb930af21c9528feed2350
Tx public key: 24903522e6b615c47aca87c6d0ad979e3c7c3a6e6f05938593dd9a2a21489b8a
Timestamp: 1731701044 Timestamp [UCT]: 2024-11-15 20:04:04 Age [y:d:h:m:s]: 00:214:23:45:51
Block: 1154465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153392 RingCT/type: yes/0
Extra: 0124903522e6b615c47aca87c6d0ad979e3c7c3a6e6f05938593dd9a2a21489b8a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dc4063277969cf783c2dabab1e0c69a8d9a19bc36d70858e767754b9b3108df 0.600000000000 1640078 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": 1154475, "vin": [ { "gen": { "height": 1154465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dc4063277969cf783c2dabab1e0c69a8d9a19bc36d70858e767754b9b3108df" } } ], "extra": [ 1, 36, 144, 53, 34, 230, 182, 21, 196, 122, 202, 135, 198, 208, 173, 151, 158, 60, 124, 58, 110, 111, 5, 147, 133, 147, 221, 154, 42, 33, 72, 155, 138, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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