Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 247023f40e0c7a5c2bdfd41fe37f0c352c9a9622f8490de500e8e0ead2455bd7

Tx prefix hash: deae3693b2e1da6c0390e73dcf0463ec914979dfac8188a24f0ace45bfba7eeb
Tx public key: 0fff9d84e68844ac5b706e743269feb58d384f913db34c64fb93147af22d7f51
Timestamp: 1728283187 Timestamp [UCT]: 2024-10-07 06:39:47 Age [y:d:h:m:s]: 01:044:21:25:15
Block: 1126230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290462 RingCT/type: yes/0
Extra: 010fff9d84e68844ac5b706e743269feb58d384f913db34c64fb93147af22d7f5102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64222e2ec116a0d93824faca1ad8f82364b1e68e1316ec9d09dc3b84dff41b64 0.600000000000 1609019 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": 1126240, "vin": [ { "gen": { "height": 1126230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64222e2ec116a0d93824faca1ad8f82364b1e68e1316ec9d09dc3b84dff41b64" } } ], "extra": [ 1, 15, 255, 157, 132, 230, 136, 68, 172, 91, 112, 110, 116, 50, 105, 254, 181, 141, 56, 79, 145, 61, 179, 76, 100, 251, 147, 20, 122, 242, 45, 127, 81, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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