Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1dab210dfe62f87b515b6d6ec23962c2ae898c92cc126bab28b926e910f62ca

Tx prefix hash: 47d10891a26d76fce8c0b9c38cd82193b9bcd7f5e72b5c93e06b25084004f8af
Tx public key: bff329e5de3f11da021c5e39fd3bdcfa7d9f8c82962ff25fd98ad1cdfa1f6616
Timestamp: 1751062587 Timestamp [UCT]: 2025-06-27 22:16:27 Age [y:d:h:m:s]: 00:142:23:11:42
Block: 1314119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100240 RingCT/type: yes/0
Extra: 01bff329e5de3f11da021c5e39fd3bdcfa7d9f8c82962ff25fd98ad1cdfa1f6616021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efd2920dbdf142b0faf9cf9a2c0d0d243a2c0ac8ea057d54d6703abe4c8bdde6 0.600000000000 1801764 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": 1314129, "vin": [ { "gen": { "height": 1314119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efd2920dbdf142b0faf9cf9a2c0d0d243a2c0ac8ea057d54d6703abe4c8bdde6" } } ], "extra": [ 1, 191, 243, 41, 229, 222, 63, 17, 218, 2, 28, 94, 57, 253, 59, 220, 250, 125, 159, 140, 130, 150, 47, 242, 95, 217, 138, 209, 205, 250, 31, 102, 22, 2, 17, 0, 0, 0, 1, 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