Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0306f3ecb2eb5cf99936d1085572afbf19fa0f45fc10e58c07852673c79d8c30

Tx prefix hash: 3f6b3935efe8450f69a5725b7b55bfad71da603e2783bc6ef1ce957e4dace42a
Tx public key: 401caf3895a8d780eb0d3269d1c2c218e94be1a5db515a7c7b64f8b80101ae01
Timestamp: 1581546384 Timestamp [UCT]: 2020-02-12 22:26:24 Age [y:d:h:m:s]: 05:262:11:34:31
Block: 63745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1338116 RingCT/type: yes/0
Extra: 01401caf3895a8d780eb0d3269d1c2c218e94be1a5db515a7c7b64f8b80101ae010211000000054ac5aa02000000000000000000

1 output(s) for total of 377.387200091000 dcy

stealth address amount amount idx
00: 3968d8ad04235ab8864ef8074852215c240eee9319ce8112c4110675dcc46caa 377.387200091000 117496 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": 63755, "vin": [ { "gen": { "height": 63745 } } ], "vout": [ { "amount": 377387200091, "target": { "key": "3968d8ad04235ab8864ef8074852215c240eee9319ce8112c4110675dcc46caa" } } ], "extra": [ 1, 64, 28, 175, 56, 149, 168, 215, 128, 235, 13, 50, 105, 209, 194, 194, 24, 233, 75, 225, 165, 219, 81, 90, 124, 123, 100, 248, 184, 1, 1, 174, 1, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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