Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 369daf7a81f0f0c409d6c6694086adc9c7126ffcf8dd2d5a3fc861d2de2f9f3b

Tx prefix hash: df4ffb54ed02ec9b262cc9c22349995496a0ec0cce3d5ab8cb1c3134b4735ae1
Tx public key: 5388a587e25d7ae3b9f8ff4e5b3d19af8b30b69ced4bcf3405ac9105952ccf3b
Timestamp: 1697321829 Timestamp [UCT]: 2023-10-14 22:17:09 Age [y:d:h:m:s]: 01:097:13:12:07
Block: 869746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330934 RingCT/type: yes/0
Extra: 015388a587e25d7ae3b9f8ff4e5b3d19af8b30b69ced4bcf3405ac9105952ccf3b02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.805694652000 dcy

stealth address amount amount idx
00: 0711358ee3c0aa5c102b57d301802ba52c8da35c8435389d8cb3998c8b330d36 0.805694652000 1324601 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": 869756, "vin": [ { "gen": { "height": 869746 } } ], "vout": [ { "amount": 805694652, "target": { "key": "0711358ee3c0aa5c102b57d301802ba52c8da35c8435389d8cb3998c8b330d36" } } ], "extra": [ 1, 83, 136, 165, 135, 226, 93, 122, 227, 185, 248, 255, 78, 91, 61, 25, 175, 139, 48, 182, 156, 237, 75, 207, 52, 5, 172, 145, 5, 149, 44, 207, 59, 2, 17, 0, 0, 0, 1, 117, 227, 240, 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