Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb8cd5a40abd821bc2580f76ade4a0aacce4d7f93d5b8fa94761a85326742865

Tx prefix hash: 2a834a68af36bf4c5ccd6d99d4d3a4a0bcc95628431d7bf797d9d39db8622f59
Tx public key: d0e3705fa187f30f55a2638c7fe1e1871c15191008b95f7d3934a4dd08e9d555
Timestamp: 1688402062 Timestamp [UCT]: 2023-07-03 16:34:22 Age [y:d:h:m:s]: 01:241:10:16:29
Block: 795854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433649 RingCT/type: yes/0
Extra: 01d0e3705fa187f30f55a2638c7fe1e1871c15191008b95f7d3934a4dd08e9d555021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.415811577000 dcy

stealth address amount amount idx
00: 5f9b8fa69946fb9cce3f74a59f07e3b94e0a5200af8b1750a6df7cc49dc3f811 1.415811577000 1246691 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": 795864, "vin": [ { "gen": { "height": 795854 } } ], "vout": [ { "amount": 1415811577, "target": { "key": "5f9b8fa69946fb9cce3f74a59f07e3b94e0a5200af8b1750a6df7cc49dc3f811" } } ], "extra": [ 1, 208, 227, 112, 95, 161, 135, 243, 15, 85, 162, 99, 140, 127, 225, 225, 135, 28, 21, 25, 16, 8, 185, 95, 125, 57, 52, 164, 221, 8, 233, 213, 85, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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