Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3194a57d8be24581cac2cf7d78f2fc7ec495e85083dcd63cf6cc2e2380ed24d5

Tx prefix hash: d01126d4e3a3b0437af9f1cd673c4bde4eecf98503f246c0159ca452a97e84fd
Tx public key: 074be0b17f9fb4697a24c3548c8b4f662eb2a0cfc836fb7da1affa4c89a4f86c
Timestamp: 1696989900 Timestamp [UCT]: 2023-10-11 02:05:00 Age [y:d:h:m:s]: 01:137:07:06:27
Block: 866999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359120 RingCT/type: yes/0
Extra: 01074be0b17f9fb4697a24c3548c8b4f662eb2a0cfc836fb7da1affa4c89a4f86c0211000000044b8f5122000000000000000000

1 output(s) for total of 0.822758611000 dcy

stealth address amount amount idx
00: 63cc9b8a3d9cabe14f216cd89943b636433f0df0921c2409bfdcb629127e5b6a 0.822758611000 1321639 of 0

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": 867009, "vin": [ { "gen": { "height": 866999 } } ], "vout": [ { "amount": 822758611, "target": { "key": "63cc9b8a3d9cabe14f216cd89943b636433f0df0921c2409bfdcb629127e5b6a" } } ], "extra": [ 1, 7, 75, 224, 177, 127, 159, 180, 105, 122, 36, 195, 84, 140, 139, 79, 102, 46, 178, 160, 207, 200, 54, 251, 125, 161, 175, 250, 76, 137, 164, 248, 108, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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