Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2705c6d8275adc13bafaafc03ab04602c472c27f7d822e1c429e93d6570605d8

Tx prefix hash: 2f8afb29aa89d45d4572452597a8abd07cd357741456e97c303a3c820c26dba4
Tx public key: 362573c681888c7a8bf315c85ebb9a03e4d4f5096a3e6c73fe66ff06006fb78f
Timestamp: 1707664593 Timestamp [UCT]: 2024-02-11 15:16:33 Age [y:d:h:m:s]: 00:360:02:57:34
Block: 955280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257531 RingCT/type: yes/0
Extra: 01362573c681888c7a8bf315c85ebb9a03e4d4f5096a3e6c73fe66ff06006fb78f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 203b93ee1d8132fb00a2384edb43892bc3663c0ac80815f4090a6e9fd37b6209 0.600000000000 1414566 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": 955290, "vin": [ { "gen": { "height": 955280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "203b93ee1d8132fb00a2384edb43892bc3663c0ac80815f4090a6e9fd37b6209" } } ], "extra": [ 1, 54, 37, 115, 198, 129, 136, 140, 122, 139, 243, 21, 200, 94, 187, 154, 3, 228, 212, 245, 9, 106, 62, 108, 115, 254, 102, 255, 6, 0, 111, 183, 143, 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