Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0245d837f4bfa7a2e14417f5cc4a0aafba8fd6bbdffbbc6568f5a480ee38370

Tx prefix hash: c52c6acc3cb26d38bdddc8f68c5e75e2a38b7d84c9000005e0eb280ced10115c
Tx public key: e36831a952b7479397d4f26b630913f9434da0c35020876a8582b2f9bc92d8b9
Timestamp: 1762746756 Timestamp [UCT]: 2025-11-10 03:52:36 Age [y:d:h:m:s]: 00:047:19:02:27
Block: 1408820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34227 RingCT/type: yes/0
Extra: 01e36831a952b7479397d4f26b630913f9434da0c35020876a8582b2f9bc92d8b9021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7721092f7477fd93bca5d26698bac9ba5baed0c5487eefdf3f2e4e0105d10aac 0.600000000000 1897251 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": 1408830, "vin": [ { "gen": { "height": 1408820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7721092f7477fd93bca5d26698bac9ba5baed0c5487eefdf3f2e4e0105d10aac" } } ], "extra": [ 1, 227, 104, 49, 169, 82, 183, 71, 147, 151, 212, 242, 107, 99, 9, 19, 249, 67, 77, 160, 195, 80, 32, 135, 106, 133, 130, 178, 249, 188, 146, 216, 185, 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