Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a3d3ccdd05a9821ee4ee089488833d6a9b02f638e38d46eb63646d013564f00

Tx prefix hash: ff9e069d056b00ffffb82080d4afc1ad800d445806aa708e76fc1f85a5f7194f
Tx public key: 15013fb1097d820a09cf6a7a95066be123160b28560bf2f7df4aa6e5261f8e4e
Timestamp: 1736931951 Timestamp [UCT]: 2025-01-15 09:05:51 Age [y:d:h:m:s]: 00:339:21:09:59
Block: 1197778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240480 RingCT/type: yes/0
Extra: 0115013fb1097d820a09cf6a7a95066be123160b28560bf2f7df4aa6e5261f8e4e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f32c5600f3d7bdfc6b09159b74c5875f3b185c9329f0f831447caa63819aa780 0.600000000000 1684395 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": 1197788, "vin": [ { "gen": { "height": 1197778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f32c5600f3d7bdfc6b09159b74c5875f3b185c9329f0f831447caa63819aa780" } } ], "extra": [ 1, 21, 1, 63, 177, 9, 125, 130, 10, 9, 207, 106, 122, 149, 6, 107, 225, 35, 22, 11, 40, 86, 11, 242, 247, 223, 74, 166, 229, 38, 31, 142, 78, 2, 17, 0, 0, 0, 6, 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