Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 629d4861fc2c90cf7a9ec3f92faea65e09739e462f5d7c33cba9a51e1982954a

Tx prefix hash: 71afa0ece2f42e1e7e72bfaaafa51f245615e886427d87fdbd306ae6446d62b0
Tx public key: ef6db87a67c4b2d5e72fd9456c548deab990113f18e4e580c4ef1bf94196b526
Timestamp: 1745344042 Timestamp [UCT]: 2025-04-22 17:47:22 Age [y:d:h:m:s]: 00:212:02:45:41
Block: 1267154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149317 RingCT/type: yes/0
Extra: 01ef6db87a67c4b2d5e72fd9456c548deab990113f18e4e580c4ef1bf94196b52602110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5b2d8fdd92bf59605f8957695fc76d20a1e862ba656cbb51d96b3c8511dbe64 0.600000000000 1754381 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": 1267164, "vin": [ { "gen": { "height": 1267154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5b2d8fdd92bf59605f8957695fc76d20a1e862ba656cbb51d96b3c8511dbe64" } } ], "extra": [ 1, 239, 109, 184, 122, 103, 196, 178, 213, 231, 47, 217, 69, 108, 84, 141, 234, 185, 144, 17, 63, 24, 228, 229, 128, 196, 239, 27, 249, 65, 150, 181, 38, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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