Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc75a7504bad62d809f59a8852e33d5681eec3e2907d11f72bdcbb28fa3e75c0

Tx prefix hash: b10408a73ad7a001329053b0df992fe706ad84a8f2c18a5b1677cd404bfbde3a
Tx public key: 7da113d3b99df35316eeb3ba8eb592cddd3456f34374bbe28e654d44795a8d3c
Timestamp: 1704583236 Timestamp [UCT]: 2024-01-06 23:20:36 Age [y:d:h:m:s]: 01:052:01:23:26
Block: 929720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298287 RingCT/type: yes/0
Extra: 017da113d3b99df35316eeb3ba8eb592cddd3456f34374bbe28e654d44795a8d3c02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72b716b10c0cbdc618a0108c9811242680ecb3dca130fe7cb92d0b49e42ff8b4 0.600000000000 1387596 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": 929730, "vin": [ { "gen": { "height": 929720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72b716b10c0cbdc618a0108c9811242680ecb3dca130fe7cb92d0b49e42ff8b4" } } ], "extra": [ 1, 125, 161, 19, 211, 185, 157, 243, 83, 22, 238, 179, 186, 142, 181, 146, 205, 221, 52, 86, 243, 67, 116, 187, 226, 142, 101, 77, 68, 121, 90, 141, 60, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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