Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e5de7bd4936c160f6ae23588141675d7411329fcdfe81fc7f77660aef578fb0

Tx prefix hash: 4bc8b4ee8b035313a1aeeb76314fe9d04336523051cf803e7bacb0afe3dc69be
Tx public key: 02e2be9d65ff28f595e4542d8b644463e5c0df432f9cf4f939b286ef108139cb
Timestamp: 1717199314 Timestamp [UCT]: 2024-05-31 23:48:34 Age [y:d:h:m:s]: 00:265:18:18:51
Block: 1034340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189885 RingCT/type: yes/0
Extra: 0102e2be9d65ff28f595e4542d8b644463e5c0df432f9cf4f939b286ef108139cb0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 943447cd8b074157c6845bd6a6cf29322077ddf2ce0d837a79bd0f54d8218bba 0.600000000000 1502843 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": 1034350, "vin": [ { "gen": { "height": 1034340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "943447cd8b074157c6845bd6a6cf29322077ddf2ce0d837a79bd0f54d8218bba" } } ], "extra": [ 1, 2, 226, 190, 157, 101, 255, 40, 245, 149, 228, 84, 45, 139, 100, 68, 99, 229, 192, 223, 67, 47, 156, 244, 249, 57, 178, 134, 239, 16, 129, 57, 203, 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