Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed69d50447652a9198c86d85eac7f805ac927c3864b2aa31f48bad26841be2ca

Tx prefix hash: 917e8a5a6e14e5eb3fc5804480f80d83aff08e313671eeb7ddee577ac2febc57
Tx public key: 8f109d122aa73d6c5cafc33b4fc1132c2595a8cd671b2ff6dc83c04769bc2a8c
Timestamp: 1712003200 Timestamp [UCT]: 2024-04-01 20:26:40 Age [y:d:h:m:s]: 01:246:08:56:03
Block: 991227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434824 RingCT/type: yes/0
Extra: 018f109d122aa73d6c5cafc33b4fc1132c2595a8cd671b2ff6dc83c04769bc2a8c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c634813ddf8ae10a5de7c90f2266ca808a36e28dee0cbc596cf864936374048 0.600000000000 1451561 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": 991237, "vin": [ { "gen": { "height": 991227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c634813ddf8ae10a5de7c90f2266ca808a36e28dee0cbc596cf864936374048" } } ], "extra": [ 1, 143, 16, 157, 18, 42, 167, 61, 108, 92, 175, 195, 59, 79, 193, 19, 44, 37, 149, 168, 205, 103, 27, 47, 246, 220, 131, 192, 71, 105, 188, 42, 140, 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