Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f7511845738fc97d96aeb8a2267576eba9c2392386531d9b03683c23f227c5c

Tx prefix hash: 4c1db98ed1efd73c5c417551d11466a8f9c23ba218c4bae4a76e5e3bf8956746
Tx public key: 356c2abfde2955d567e9f2656b65aa57ffe5011ba0de1df97c3dde8244f30ea8
Timestamp: 1725323296 Timestamp [UCT]: 2024-09-03 00:28:16 Age [y:d:h:m:s]: 00:086:13:53:47
Block: 1101689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61923 RingCT/type: yes/0
Extra: 01356c2abfde2955d567e9f2656b65aa57ffe5011ba0de1df97c3dde8244f30ea8021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e31df593ce05754506b97b703ab76fe75b097da4481c5344213e1f6ea39576c 0.600000000000 1577836 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": 1101699, "vin": [ { "gen": { "height": 1101689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e31df593ce05754506b97b703ab76fe75b097da4481c5344213e1f6ea39576c" } } ], "extra": [ 1, 53, 108, 42, 191, 222, 41, 85, 213, 103, 233, 242, 101, 107, 101, 170, 87, 255, 229, 1, 27, 160, 222, 29, 249, 124, 61, 222, 130, 68, 243, 14, 168, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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