Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85489cb3e930b8496a100ffff8551e714ec1ea1cd4c5033d85dcfdc47f1b07bf

Tx prefix hash: 37e9b44d657426a86d122a7e757c7d58aa431493838b5dd3b2a8c60e7ad2ba8d
Tx public key: 31e80db9d45687490f7b8e260723403265efad9a9a9dde0bc2c152e5b6280d4f
Timestamp: 1732557922 Timestamp [UCT]: 2024-11-25 18:05:22 Age [y:d:h:m:s]: 00:119:06:28:42
Block: 1161566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85041 RingCT/type: yes/0
Extra: 0131e80db9d45687490f7b8e260723403265efad9a9a9dde0bc2c152e5b6280d4f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a8f767d98e420dba7778a33d8e756623dc4a8747545303f1afd68a296c23efe 0.600000000000 1647221 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": 1161576, "vin": [ { "gen": { "height": 1161566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a8f767d98e420dba7778a33d8e756623dc4a8747545303f1afd68a296c23efe" } } ], "extra": [ 1, 49, 232, 13, 185, 212, 86, 135, 73, 15, 123, 142, 38, 7, 35, 64, 50, 101, 239, 173, 154, 154, 157, 222, 11, 194, 193, 82, 229, 182, 40, 13, 79, 2, 17, 0, 0, 0, 3, 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