Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbfb0942269cd205402dd1d035a743a3b95dc027e411c42f216bece15abefe61

Tx prefix hash: 3ae456dc0e972665f47e875b0f661065c06a6d78a53ee3d371da850d61a34654
Tx public key: ba8e54f1cbc3f490e831f1024561cf6256ad35375f0e74695ac2bfe3730a90de
Timestamp: 1711826442 Timestamp [UCT]: 2024-03-30 19:20:42 Age [y:d:h:m:s]: 01:008:00:44:33
Block: 989816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266668 RingCT/type: yes/0
Extra: 01ba8e54f1cbc3f490e831f1024561cf6256ad35375f0e74695ac2bfe3730a90de0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39915466ccbc5f862bf23c057c582734aa9784d5d7db4fb577a69b88b41ff30c 0.600000000000 1450134 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": 989826, "vin": [ { "gen": { "height": 989816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39915466ccbc5f862bf23c057c582734aa9784d5d7db4fb577a69b88b41ff30c" } } ], "extra": [ 1, 186, 142, 84, 241, 203, 195, 244, 144, 232, 49, 241, 2, 69, 97, 207, 98, 86, 173, 53, 55, 95, 14, 116, 105, 90, 194, 191, 227, 115, 10, 144, 222, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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