Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81802242ccb7694383d5f541e82c269bbbbb2c7dc3b23f72b05efcd61671b4d0

Tx prefix hash: b114071687fa86171cf9d3ce971f9ef1862a4838abb9129c058fe47ddb8b76b2
Tx public key: dbef3bc86058a5e8cf98dadfd61fa64fb38015bc8d3a5467b245b6f31f075d12
Timestamp: 1708303034 Timestamp [UCT]: 2024-02-19 00:37:14 Age [y:d:h:m:s]: 01:288:20:26:12
Block: 960575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465233 RingCT/type: yes/0
Extra: 01dbef3bc86058a5e8cf98dadfd61fa64fb38015bc8d3a5467b245b6f31f075d1202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b84de01d0b3169bc185f6e446edfd0cdf4400af0b381993ede1f37479f2aeae 0.600000000000 1420160 of 15

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": 960585, "vin": [ { "gen": { "height": 960575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b84de01d0b3169bc185f6e446edfd0cdf4400af0b381993ede1f37479f2aeae" } } ], "extra": [ 1, 219, 239, 59, 200, 96, 88, 165, 232, 207, 152, 218, 223, 214, 31, 166, 79, 179, 128, 21, 188, 141, 58, 84, 103, 178, 69, 182, 243, 31, 7, 93, 18, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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