Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9d122bc1c8c8d742e33bafc3d3a18b6ebe928c77e2a2448545c47f4ed4c405d

Tx prefix hash: 236be9af44651b94016793f5a78dde02e1c320c6e5877e41788e00a95639e077
Tx public key: eae9641d02248b8b306708fa4c119c223214af7aff70e560de0c4d0faf0cc71e
Timestamp: 1733056551 Timestamp [UCT]: 2024-12-01 12:35:51 Age [y:d:h:m:s]: 00:131:10:03:03
Block: 1165707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93735 RingCT/type: yes/0
Extra: 01eae9641d02248b8b306708fa4c119c223214af7aff70e560de0c4d0faf0cc71e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1d4a14e5b9f642b74f2266868723a8f283d8695b5a6219250fd41e2e47df6bf 0.600000000000 1651382 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": 1165717, "vin": [ { "gen": { "height": 1165707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1d4a14e5b9f642b74f2266868723a8f283d8695b5a6219250fd41e2e47df6bf" } } ], "extra": [ 1, 234, 233, 100, 29, 2, 36, 139, 139, 48, 103, 8, 250, 76, 17, 156, 34, 50, 20, 175, 122, 255, 112, 229, 96, 222, 12, 77, 15, 175, 12, 199, 30, 2, 17, 0, 0, 0, 3, 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