Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b913d725d39f47a44e3d3e1ca72aae389654362ba28e21008043dc76cd1ffdd

Tx prefix hash: 55362e462dec7fafdb1fe407b295f1883b01cbda8c4752374923ff1c6eb801f9
Tx public key: c504f1e6d215bd37e39f355d7027f8dc13e3264214b16cc9ff555cd37c8ef202
Timestamp: 1735287663 Timestamp [UCT]: 2024-12-27 08:21:03 Age [y:d:h:m:s]: 00:102:03:42:01
Block: 1184166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72795 RingCT/type: yes/0
Extra: 01c504f1e6d215bd37e39f355d7027f8dc13e3264214b16cc9ff555cd37c8ef2020211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72d2265a46befb9c7b07258ead9995dd580b752a87b04a712129902319fcf508 0.600000000000 1670621 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": 1184176, "vin": [ { "gen": { "height": 1184166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72d2265a46befb9c7b07258ead9995dd580b752a87b04a712129902319fcf508" } } ], "extra": [ 1, 197, 4, 241, 230, 210, 21, 189, 55, 227, 159, 53, 93, 112, 39, 248, 220, 19, 227, 38, 66, 20, 177, 108, 201, 255, 85, 92, 211, 124, 142, 242, 2, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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