Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd9b4819cfe2d4b2f5926157d04e011128cb839a5753045cb857a913397385e0

Tx prefix hash: 0cc73c9b27f4caeff1ab15805232775410908f40520434f9cba4484cece76228
Tx public key: 0c0ff9f024cd3401e5d9dd9a1beff06b43cfed841a49aaa50373d1f5907b1b68
Timestamp: 1617251825 Timestamp [UCT]: 2021-04-01 04:37:05 Age [y:d:h:m:s]: 03:289:12:01:33
Block: 230882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 966419 RingCT/type: yes/0
Extra: 010c0ff9f024cd3401e5d9dd9a1beff06b43cfed841a49aaa50373d1f5907b1b6802110000005ef18a1c63000000000000000000

1 output(s) for total of 105.446020218000 dcy

stealth address amount amount idx
00: 342bdea94bd987d74680fb762d748c3e2f80f7417001ce80a74d0a523599f548 105.446020218000 479344 of 0

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": 230892, "vin": [ { "gen": { "height": 230882 } } ], "vout": [ { "amount": 105446020218, "target": { "key": "342bdea94bd987d74680fb762d748c3e2f80f7417001ce80a74d0a523599f548" } } ], "extra": [ 1, 12, 15, 249, 240, 36, 205, 52, 1, 229, 217, 221, 154, 27, 239, 240, 107, 67, 207, 237, 132, 26, 73, 170, 165, 3, 115, 209, 245, 144, 123, 27, 104, 2, 17, 0, 0, 0, 94, 241, 138, 28, 99, 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