Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e8bb4b4a4db7db80392e0b50552df2c55d4c7b5dca2d544715aea586f32fa99

Tx prefix hash: 9ee16f5a9d71f0249474599499abea9ad8b71326b87de3da64b797d0bdb2b9f1
Tx public key: 24f92ce08013e68691d0e335bb7052c1d60246a13be101e81b5c09471c51f45a
Timestamp: 1700476412 Timestamp [UCT]: 2023-11-20 10:33:32 Age [y:d:h:m:s]: 01:175:01:49:07
Block: 895693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386324 RingCT/type: yes/0
Extra: 0124f92ce08013e68691d0e335bb7052c1d60246a13be101e81b5c09471c51f45a02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.660993610000 dcy

stealth address amount amount idx
00: 99adf951b9534d7592a24625f5bba45e67fc2dfe0f6bf3171050d076f60b30b1 0.660993610000 1351934 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": 895703, "vin": [ { "gen": { "height": 895693 } } ], "vout": [ { "amount": 660993610, "target": { "key": "99adf951b9534d7592a24625f5bba45e67fc2dfe0f6bf3171050d076f60b30b1" } } ], "extra": [ 1, 36, 249, 44, 224, 128, 19, 230, 134, 145, 208, 227, 53, 187, 112, 82, 193, 214, 2, 70, 161, 59, 225, 1, 232, 27, 92, 9, 71, 28, 81, 244, 90, 2, 17, 0, 0, 0, 2, 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