Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3a872c361a55f6f6a00d4266bcd182a6d4b409e6878974972e8755e900140e1

Tx prefix hash: 0f8c5fb21edb720b520543345f729a3819a499686b8d915b9cd63c194b7e50be
Tx public key: 41f340d2321e88c71314472d3aab6967eb35df1c5cd4f4b6dde106ad93a0ed36
Timestamp: 1707990188 Timestamp [UCT]: 2024-02-15 09:43:08 Age [y:d:h:m:s]: 00:334:02:15:39
Block: 957985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239167 RingCT/type: yes/0
Extra: 0141f340d2321e88c71314472d3aab6967eb35df1c5cd4f4b6dde106ad93a0ed3602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc95ae3a6e1f7c812f430bee01013db74c31076bf19f743f5d720af1f3b8f613 0.600000000000 1417336 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": 957995, "vin": [ { "gen": { "height": 957985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc95ae3a6e1f7c812f430bee01013db74c31076bf19f743f5d720af1f3b8f613" } } ], "extra": [ 1, 65, 243, 64, 210, 50, 30, 136, 199, 19, 20, 71, 45, 58, 171, 105, 103, 235, 53, 223, 28, 92, 212, 244, 182, 221, 225, 6, 173, 147, 160, 237, 54, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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