Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a825c6368cef08138bb67e2f00cf0b31f6c0bdf549b8ba2ca37fc45d035f48d8

Tx prefix hash: 1693ebc6e77d3995214d61769e62000798cc341f6010fa1707da0aecdd4928ec
Tx public key: e9f5300332c18bd2c5079d98eb9df4d2a8daedb1bc404d0693e71ea9f6565709
Timestamp: 1728754424 Timestamp [UCT]: 2024-10-12 17:33:44 Age [y:d:h:m:s]: 00:176:05:56:50
Block: 1130139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125729 RingCT/type: yes/0
Extra: 01e9f5300332c18bd2c5079d98eb9df4d2a8daedb1bc404d0693e71ea9f656570902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1922de7d84d80bbe81e864818341dd8efdf8b70e0e790d13996b2d3c2faee596 0.600000000000 1613012 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": 1130149, "vin": [ { "gen": { "height": 1130139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1922de7d84d80bbe81e864818341dd8efdf8b70e0e790d13996b2d3c2faee596" } } ], "extra": [ 1, 233, 245, 48, 3, 50, 193, 139, 210, 197, 7, 157, 152, 235, 157, 244, 210, 168, 218, 237, 177, 188, 64, 77, 6, 147, 231, 30, 169, 246, 86, 87, 9, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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