Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71ab38454a62a66bce1e42f36bbcf15c51b8a5c329c937a7e8541be52f31feb9

Tx prefix hash: cfce3b040b06f5f6c8d1efd0bca2cbb3d7956c48549a7d0c3f12b645043be467
Tx public key: d85423f95b498827a4119f2781503310248b232c11e49da9e9461f8f14c425ca
Timestamp: 1762923541 Timestamp [UCT]: 2025-11-12 04:59:01 Age [y:d:h:m:s]: 00:041:23:39:03
Block: 1410286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30053 RingCT/type: yes/0
Extra: 01d85423f95b498827a4119f2781503310248b232c11e49da9e9461f8f14c425ca02110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7a2221fde4a365a8d7bb3f1326dcdee633e3a8fc0b5197a1dfad7b89fdf8b55 0.600000000000 1898737 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": 1410296, "vin": [ { "gen": { "height": 1410286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7a2221fde4a365a8d7bb3f1326dcdee633e3a8fc0b5197a1dfad7b89fdf8b55" } } ], "extra": [ 1, 216, 84, 35, 249, 91, 73, 136, 39, 164, 17, 159, 39, 129, 80, 51, 16, 36, 139, 35, 44, 17, 228, 157, 169, 233, 70, 31, 143, 20, 196, 37, 202, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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