Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1da50fcd8d121836e50b0e2b79080dc4af25dfa2c2f5a4151164cab25108d90

Tx prefix hash: 719f306051320e1cf3c050e0a8cc118c67c502ff401b608811ff24a1be11421f
Tx public key: dff2d9b17bf100c7e8a385a30aeb9af2282b387c217b808f1ce0e9d1c998bbca
Timestamp: 1749614965 Timestamp [UCT]: 2025-06-11 04:09:25 Age [y:d:h:m:s]: 00:156:06:05:10
Block: 1302510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109369 RingCT/type: yes/0
Extra: 01dff2d9b17bf100c7e8a385a30aeb9af2282b387c217b808f1ce0e9d1c998bbca021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e3f99c32390410e28fa47f6253919b6de31097583ae609937be7c99da8c3592 0.600000000000 1790081 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": 1302520, "vin": [ { "gen": { "height": 1302510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e3f99c32390410e28fa47f6253919b6de31097583ae609937be7c99da8c3592" } } ], "extra": [ 1, 223, 242, 217, 177, 123, 241, 0, 199, 232, 163, 133, 163, 10, 235, 154, 242, 40, 43, 56, 124, 33, 123, 128, 143, 28, 224, 233, 209, 201, 152, 187, 202, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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