Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9659dab09021501e811adc6a040b92cb76594cc25046af898b73af1b3a01400

Tx prefix hash: 7e068c78c0f75f991b5e05db3343d8bda4dec739a2a43f093f01e7c16ae49e5c
Tx public key: a0cff837dc2abfb3009156ec90114e21da0e7f06460d61cba34cc68d6d9f58fa
Timestamp: 1733354329 Timestamp [UCT]: 2024-12-04 23:18:49 Age [y:d:h:m:s]: 00:111:12:08:03
Block: 1168166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79470 RingCT/type: yes/0
Extra: 01a0cff837dc2abfb3009156ec90114e21da0e7f06460d61cba34cc68d6d9f58fa0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bec94c85f5985ba86103e2aa5cde292687c32b90b765439e5d66d0cbc11f1af 0.600000000000 1653873 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": 1168176, "vin": [ { "gen": { "height": 1168166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bec94c85f5985ba86103e2aa5cde292687c32b90b765439e5d66d0cbc11f1af" } } ], "extra": [ 1, 160, 207, 248, 55, 220, 42, 191, 179, 0, 145, 86, 236, 144, 17, 78, 33, 218, 14, 127, 6, 70, 13, 97, 203, 163, 76, 198, 141, 109, 159, 88, 250, 2, 17, 0, 0, 0, 7, 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