Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d70b452eb949ae896e0e245b25d5667cfa1d072fa8cb3b7c47a464616fd9009c

Tx prefix hash: 12cd91b9eb777917838512bc8a70f8de6e3ff86058d43854f75861d6753a82af
Tx public key: a3e461aa799cd150d294d67522a432ed4a2f2d1d2de96ae8b60a043346ebbc9f
Timestamp: 1660929053 Timestamp [UCT]: 2022-08-19 17:10:53 Age [y:d:h:m:s]: 02:227:09:49:03
Block: 569376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 683739 RingCT/type: yes/0
Extra: 01a3e461aa799cd150d294d67522a432ed4a2f2d1d2de96ae8b60a043346ebbc9f021100000023e6d27f9c000000000000000000

1 output(s) for total of 7.969316162000 dcy

stealth address amount amount idx
00: 69abadc48d4e8ee7679564aa5a2277f4f2b1ad6eb2b381837ba5b744c7b1b9d6 7.969316162000 1002521 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": 569386, "vin": [ { "gen": { "height": 569376 } } ], "vout": [ { "amount": 7969316162, "target": { "key": "69abadc48d4e8ee7679564aa5a2277f4f2b1ad6eb2b381837ba5b744c7b1b9d6" } } ], "extra": [ 1, 163, 228, 97, 170, 121, 156, 209, 80, 210, 148, 214, 117, 34, 164, 50, 237, 74, 47, 45, 29, 45, 233, 106, 232, 182, 10, 4, 51, 70, 235, 188, 159, 2, 17, 0, 0, 0, 35, 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