Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c31e19aa7f588ee97d2eae028bdcf8b4844a86f73d56056794872c60aada3c67

Tx prefix hash: 136872cfee6111e7111fac31545b03bb3dec35f29cbefba993c5e8e164a0744c
Tx public key: 92d65e7dc48936f2658a0daa633ca0a682f480172e6c40c4cd8471776f765e7c
Timestamp: 1726924335 Timestamp [UCT]: 2024-09-21 13:12:15 Age [y:d:h:m:s]: 00:199:04:51:33
Block: 1114969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142172 RingCT/type: yes/0
Extra: 0192d65e7dc48936f2658a0daa633ca0a682f480172e6c40c4cd8471776f765e7c02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1454dae6e6f65a9c2dfac2c17ea26434dc3a485c50bd04ae0bb4caf7ecd5fd9 0.600000000000 1594934 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": 1114979, "vin": [ { "gen": { "height": 1114969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1454dae6e6f65a9c2dfac2c17ea26434dc3a485c50bd04ae0bb4caf7ecd5fd9" } } ], "extra": [ 1, 146, 214, 94, 125, 196, 137, 54, 242, 101, 138, 13, 170, 99, 60, 160, 166, 130, 244, 128, 23, 46, 108, 64, 196, 205, 132, 113, 119, 111, 118, 94, 124, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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