Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82928a12b3360a1d0293836448c494318501693bc539d70eaee609daa6c580e2

Tx prefix hash: 36b3a490986f948f34aa5580f45bee91f679b5f31c0a3dde87d9b9c7eb63bb9b
Tx public key: e64b8af50d5065ab8d3627a5cd06da4ba1812e1b41b18b2e97b1e53612cb5cd3
Timestamp: 1708285317 Timestamp [UCT]: 2024-02-18 19:41:57 Age [y:d:h:m:s]: 01:095:00:09:13
Block: 960439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328964 RingCT/type: yes/0
Extra: 01e64b8af50d5065ab8d3627a5cd06da4ba1812e1b41b18b2e97b1e53612cb5cd302110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beace94ff4e685f62ea0b12dd6ecbb07ec886de01462f3d95e8c7ce4e7a83824 0.600000000000 1420004 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": 960449, "vin": [ { "gen": { "height": 960439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beace94ff4e685f62ea0b12dd6ecbb07ec886de01462f3d95e8c7ce4e7a83824" } } ], "extra": [ 1, 230, 75, 138, 245, 13, 80, 101, 171, 141, 54, 39, 165, 205, 6, 218, 75, 161, 129, 46, 27, 65, 177, 139, 46, 151, 177, 229, 54, 18, 203, 92, 211, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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