Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc8afc2462a06e0b38f3f6e997edc6fc832fc0789c1cd846b45e67a7d0de32b3

Tx prefix hash: 21e505c9ed4fa868ee48baffc8f9043d24bbfdebd2af8996b67b4254bdd6fc72
Tx public key: 5a3fa68c8e0dc49a04d2faf6a8e36a9562d26ce50d980617f7e004f7f4f60045
Timestamp: 1736351825 Timestamp [UCT]: 2025-01-08 15:57:05 Age [y:d:h:m:s]: 00:343:04:04:07
Block: 1192979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242811 RingCT/type: yes/0
Extra: 015a3fa68c8e0dc49a04d2faf6a8e36a9562d26ce50d980617f7e004f7f4f600450211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b84147942c511ba6d2c42919b1b80c9f7edebad40d589bfd5734d1a349965099 0.600000000000 1679536 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": 1192989, "vin": [ { "gen": { "height": 1192979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b84147942c511ba6d2c42919b1b80c9f7edebad40d589bfd5734d1a349965099" } } ], "extra": [ 1, 90, 63, 166, 140, 142, 13, 196, 154, 4, 210, 250, 246, 168, 227, 106, 149, 98, 210, 108, 229, 13, 152, 6, 23, 247, 224, 4, 247, 244, 246, 0, 69, 2, 17, 0, 0, 0, 1, 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