Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd3ac8a73d8baca10c579f18791e4d1a9ba1122cede70b3edc2d38fcbb631377

Tx prefix hash: 853effcc0e13904e8deae29ea324bf69cc64d25bd2a851d360c4cceb956a8eda
Tx public key: 96ab44ccbfbc6b5b80ea90ad50038b3499e9f57dbcb136a5a67b0d67a18d1776
Timestamp: 1760997848 Timestamp [UCT]: 2025-10-20 22:04:08 Age [y:d:h:m:s]: 00:071:17:25:32
Block: 1394347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51338 RingCT/type: yes/0
Extra: 0196ab44ccbfbc6b5b80ea90ad50038b3499e9f57dbcb136a5a67b0d67a18d1776021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b43ad9027d5547d28b3f150b51fbc7cdd396c45aae71a28d0d545ecca5775b7b 0.600000000000 1882618 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": 1394357, "vin": [ { "gen": { "height": 1394347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b43ad9027d5547d28b3f150b51fbc7cdd396c45aae71a28d0d545ecca5775b7b" } } ], "extra": [ 1, 150, 171, 68, 204, 191, 188, 107, 91, 128, 234, 144, 173, 80, 3, 139, 52, 153, 233, 245, 125, 188, 177, 54, 165, 166, 123, 13, 103, 161, 141, 23, 118, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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