Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b044d71a0c3abe561faa4d3468e8f254b5e834baf1e946475cb87d5fc0338e2

Tx prefix hash: 847143071f878f79f341fb763999b429bf7f1e17c78f286c9483a85795b981b2
Tx public key: 7cf4c801450f4b5dbdacd5ba2724fcabd4922eac3f460cb116bbd73a80d1f46f
Timestamp: 1716213944 Timestamp [UCT]: 2024-05-20 14:05:44 Age [y:d:h:m:s]: 00:337:02:18:42
Block: 1026171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240950 RingCT/type: yes/0
Extra: 017cf4c801450f4b5dbdacd5ba2724fcabd4922eac3f460cb116bbd73a80d1f46f021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 286a2144a95f68405949d1a2609982866b56f6c216e717b7bfadbaee329440bc 0.600000000000 1493108 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": 1026181, "vin": [ { "gen": { "height": 1026171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "286a2144a95f68405949d1a2609982866b56f6c216e717b7bfadbaee329440bc" } } ], "extra": [ 1, 124, 244, 200, 1, 69, 15, 75, 93, 189, 172, 213, 186, 39, 36, 252, 171, 212, 146, 46, 172, 63, 70, 12, 177, 22, 187, 215, 58, 128, 209, 244, 111, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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