Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd46f91adcb3125ff2fa8bcae139f1a45e6a151faf718a0a3eda4dda70d0a124

Tx prefix hash: fa472cc2d8fd9cd0ba2165fb9b14113b82e36214f78976065769bf93d6b76dd0
Tx public key: 32e1d7ef06b7dd618da1c9116116cced686dc111fba353356d8a80024f25de19
Timestamp: 1755280533 Timestamp [UCT]: 2025-08-15 17:55:33 Age [y:d:h:m:s]: 00:129:16:43:34
Block: 1347347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92450 RingCT/type: yes/0
Extra: 0132e1d7ef06b7dd618da1c9116116cced686dc111fba353356d8a80024f25de19021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c988fd2d53c3f5d883e3bae243f7ab5da1cfdaad2e7fcc88ec8a7761a6e6efbf 0.600000000000 1835264 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": 1347357, "vin": [ { "gen": { "height": 1347347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c988fd2d53c3f5d883e3bae243f7ab5da1cfdaad2e7fcc88ec8a7761a6e6efbf" } } ], "extra": [ 1, 50, 225, 215, 239, 6, 183, 221, 97, 141, 161, 201, 17, 97, 22, 204, 237, 104, 109, 193, 17, 251, 163, 83, 53, 109, 138, 128, 2, 79, 37, 222, 25, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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