Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09734ccfa96759ce228675e1b63229a9a318b7b08f2f885b352be1b77dd54428

Tx prefix hash: b3ef42a55114860845cedb3a7e9b094bf77160dcdd696f9fafe8e4df3c639383
Tx public key: 57c5af2782d7901a8f324e6c5d7f910d789854f64acd353d0cc195ecd3f9583e
Timestamp: 1633198228 Timestamp [UCT]: 2021-10-02 18:10:28 Age [y:d:h:m:s]: 03:088:11:36:17
Block: 345337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 840183 RingCT/type: yes/0
Extra: 0157c5af2782d7901a8f324e6c5d7f910d789854f64acd353d0cc195ecd3f9583e021100000007fdc024ec000000000000000000

1 output(s) for total of 44.032430267000 dcy

stealth address amount amount idx
00: 00365780479313959c220b819c3c953f9c865d209d18c96490fd3f870911fa43 44.032430267000 708455 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": 345347, "vin": [ { "gen": { "height": 345337 } } ], "vout": [ { "amount": 44032430267, "target": { "key": "00365780479313959c220b819c3c953f9c865d209d18c96490fd3f870911fa43" } } ], "extra": [ 1, 87, 197, 175, 39, 130, 215, 144, 26, 143, 50, 78, 108, 93, 127, 145, 13, 120, 152, 84, 246, 74, 205, 53, 61, 12, 193, 149, 236, 211, 249, 88, 62, 2, 17, 0, 0, 0, 7, 253, 192, 36, 236, 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