Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d10e5b80fe9a054fce47aadc5f1562ae5db8491e9dacd7a7abcec75d7a32254

Tx prefix hash: 758667e45fa3c35bf3ea3eec48e77eb25ed2b8c1a853a2bfd1714bd0fd9afa9b
Tx public key: ed91ac9db5700f69c2600c42e8f444e62147b93910324c80d3216c7c6edb4b3c
Timestamp: 1732538799 Timestamp [UCT]: 2024-11-25 12:46:39 Age [y:d:h:m:s]: 00:156:00:29:22
Block: 1161412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111329 RingCT/type: yes/0
Extra: 01ed91ac9db5700f69c2600c42e8f444e62147b93910324c80d3216c7c6edb4b3c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a637222dad7508c53e8749d1020b9891db94ca30b7596210a10f321443071bc8 0.600000000000 1647067 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": 1161422, "vin": [ { "gen": { "height": 1161412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a637222dad7508c53e8749d1020b9891db94ca30b7596210a10f321443071bc8" } } ], "extra": [ 1, 237, 145, 172, 157, 181, 112, 15, 105, 194, 96, 12, 66, 232, 244, 68, 230, 33, 71, 185, 57, 16, 50, 76, 128, 211, 33, 108, 124, 110, 219, 75, 60, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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