Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92cab596851fb4b84126937e654ec6d12198c293fba4f11b09c98a23e53d535b

Tx prefix hash: 65fb7000114667093ebb3d55edc9cd59d17f61045ac0f27ac2f8fc932d883f12
Tx public key: 6b2340efbe6947645157b8f95c9ff418f5e3179e4ce28aa845454dae01662f7a
Timestamp: 1659138679 Timestamp [UCT]: 2022-07-29 23:51:19 Age [y:d:h:m:s]: 03:094:22:44:40
Block: 554597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 847633 RingCT/type: yes/0
Extra: 016b2340efbe6947645157b8f95c9ff418f5e3179e4ce28aa845454dae01662f7a021100000002e6d27f9c000000000000000000

1 output(s) for total of 8.920517312000 dcy

stealth address amount amount idx
00: 18c36ee09743647b8bf38dd4e473032601070026516816e4c5dd10b50a2fe943 8.920517312000 986453 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": 554607, "vin": [ { "gen": { "height": 554597 } } ], "vout": [ { "amount": 8920517312, "target": { "key": "18c36ee09743647b8bf38dd4e473032601070026516816e4c5dd10b50a2fe943" } } ], "extra": [ 1, 107, 35, 64, 239, 190, 105, 71, 100, 81, 87, 184, 249, 92, 159, 244, 24, 245, 227, 23, 158, 76, 226, 138, 168, 69, 69, 77, 174, 1, 102, 47, 122, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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