Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53e98726c488bf8a4888231727c52df920159e3d270021e4414d6cb3c93cef7e

Tx prefix hash: 5c45767888acaccf48433184aff0298f5118b678742005f6e9f3ec8775873f39
Tx public key: 8add4513fa8b4551f3cde5bc74b2d62b006476073fb4cb7285b6dc60f6b001c7
Timestamp: 1735863445 Timestamp [UCT]: 2025-01-03 00:17:25 Age [y:d:h:m:s]: 00:090:22:13:12
Block: 1188941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64751 RingCT/type: yes/0
Extra: 018add4513fa8b4551f3cde5bc74b2d62b006476073fb4cb7285b6dc60f6b001c702110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13845e0ed9c511acafee20b60e084e18a2529aae6729c4db107ebc231bb0c98a 0.600000000000 1675446 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": 1188951, "vin": [ { "gen": { "height": 1188941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13845e0ed9c511acafee20b60e084e18a2529aae6729c4db107ebc231bb0c98a" } } ], "extra": [ 1, 138, 221, 69, 19, 250, 139, 69, 81, 243, 205, 229, 188, 116, 178, 214, 43, 0, 100, 118, 7, 63, 180, 203, 114, 133, 182, 220, 96, 246, 176, 1, 199, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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