Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d69bf58acf9caa5f6d25a4a19850619d850446eadd6267cf77cf865e388de36a

Tx prefix hash: afb077e56343e9f06dc1b72a45012a81d97339070d09b3d2ac4cafd9fa1a9ccd
Tx public key: 8f785e48eab09dac64e10dc853e4ece98ecb9337d34c80ad71e4fc88ada3d3a2
Timestamp: 1763482347 Timestamp [UCT]: 2025-11-18 16:12:27 Age [y:d:h:m:s]: 00:034:17:44:27
Block: 1414918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24865 RingCT/type: yes/0
Extra: 018f785e48eab09dac64e10dc853e4ece98ecb9337d34c80ad71e4fc88ada3d3a2021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71f2e7fa6ba1eeb3cfa6966e9b71599a2335c12817140a4ad2cec30a5fe2f673 0.600000000000 1903411 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": 1414928, "vin": [ { "gen": { "height": 1414918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71f2e7fa6ba1eeb3cfa6966e9b71599a2335c12817140a4ad2cec30a5fe2f673" } } ], "extra": [ 1, 143, 120, 94, 72, 234, 176, 157, 172, 100, 225, 13, 200, 83, 228, 236, 233, 142, 203, 147, 55, 211, 76, 128, 173, 113, 228, 252, 136, 173, 163, 211, 162, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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