Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4335f7289f6d00ef55508e2edad7bdb44a8badce0fd4e4ffe63c56389b2a28d

Tx prefix hash: faac8c79b942eded8c8b32217e423bb4daf1adbb840e8733d6dfc0f45d18b39a
Tx public key: 368e2230f26d95c4b01f0656569742039e7a83be1250190efd78446dc61a144a
Timestamp: 1713765299 Timestamp [UCT]: 2024-04-22 05:54:59 Age [y:d:h:m:s]: 00:351:12:27:05
Block: 1005863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251287 RingCT/type: yes/0
Extra: 01368e2230f26d95c4b01f0656569742039e7a83be1250190efd78446dc61a144a0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f63cb981d7938acde241f3f09beadf305a7c6e05d66f4900db9f5f76d2e4c60 0.600000000000 1466689 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": 1005873, "vin": [ { "gen": { "height": 1005863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f63cb981d7938acde241f3f09beadf305a7c6e05d66f4900db9f5f76d2e4c60" } } ], "extra": [ 1, 54, 142, 34, 48, 242, 109, 149, 196, 176, 31, 6, 86, 86, 151, 66, 3, 158, 122, 131, 190, 18, 80, 25, 14, 253, 120, 68, 109, 198, 26, 20, 74, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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