Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00cf6f616d20205ac0abb75166bf9f657c8b8503a0a75a460fe025ee0f8e6b93

Tx prefix hash: 0c31694646ff0fb238fdf0f289547c6ff1eb65a92cf75a113f9164e9d0a33622
Tx public key: 9e1f3303988cd35f32843c5f8f49c2e66218b07efdea41f04d4a6039a940e032
Timestamp: 1734019818 Timestamp [UCT]: 2024-12-12 16:10:18 Age [y:d:h:m:s]: 00:099:13:02:09
Block: 1173698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70911 RingCT/type: yes/0
Extra: 019e1f3303988cd35f32843c5f8f49c2e66218b07efdea41f04d4a6039a940e0320211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fa2b9734037ded83af0abb90296eb169886a348637dbc92bcc063dc6a6dd8d8 0.600000000000 1659749 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": 1173708, "vin": [ { "gen": { "height": 1173698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fa2b9734037ded83af0abb90296eb169886a348637dbc92bcc063dc6a6dd8d8" } } ], "extra": [ 1, 158, 31, 51, 3, 152, 140, 211, 95, 50, 132, 60, 95, 143, 73, 194, 230, 98, 24, 176, 126, 253, 234, 65, 240, 77, 74, 96, 57, 169, 64, 224, 50, 2, 17, 0, 0, 0, 9, 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