Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06d86490a4c8fed2bff5bfdbd199751bfc781086fb7b748b2299dc18c53f3337

Tx prefix hash: 0e6370790442274e82ffc53f67b11684e30d9a03f185f77a9ee6cce040f01971
Tx public key: 3ddf649a21ca16eb6d02470ecf1206d336a464e88d066a1fe88c91bf8c4bf9c3
Timestamp: 1626770637 Timestamp [UCT]: 2021-07-20 08:43:57 Age [y:d:h:m:s]: 03:160:13:03:36
Block: 297475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 886382 RingCT/type: yes/0
Extra: 013ddf649a21ca16eb6d02470ecf1206d336a464e88d066a1fe88c91bf8c4bf9c30211000000556367b7e9000000000000000000

1 output(s) for total of 63.438055431000 dcy

stealth address amount amount idx
00: a2ae1ab9394505598af14680fcd63c29cf87f127802d6c9e12e2e2357ac16fa1 63.438055431000 622595 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": 297485, "vin": [ { "gen": { "height": 297475 } } ], "vout": [ { "amount": 63438055431, "target": { "key": "a2ae1ab9394505598af14680fcd63c29cf87f127802d6c9e12e2e2357ac16fa1" } } ], "extra": [ 1, 61, 223, 100, 154, 33, 202, 22, 235, 109, 2, 71, 14, 207, 18, 6, 211, 54, 164, 100, 232, 141, 6, 106, 31, 232, 140, 145, 191, 140, 75, 249, 195, 2, 17, 0, 0, 0, 85, 99, 103, 183, 233, 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