Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ae8bbdc6faca72fca451fb469b0fe046b2dd61eddc2d916f0754617ebc467d0

Tx prefix hash: e1c6635d682ea31958eddeac5bb657fe3f9b60c7c41f4755f6ccf9d81f9aadfb
Tx public key: c7dd5a4f16aa121732fd47a448899d7a929cf80c3bb4297cddd63ade9e7cdd23
Timestamp: 1704592480 Timestamp [UCT]: 2024-01-07 01:54:40 Age [y:d:h:m:s]: 01:334:04:54:50
Block: 929794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497729 RingCT/type: yes/0
Extra: 01c7dd5a4f16aa121732fd47a448899d7a929cf80c3bb4297cddd63ade9e7cdd2302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15d263e8cc741715da8d025496d292d48b9838bddeb0b76a18e4578058da37f1 0.600000000000 1387670 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": 929804, "vin": [ { "gen": { "height": 929794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15d263e8cc741715da8d025496d292d48b9838bddeb0b76a18e4578058da37f1" } } ], "extra": [ 1, 199, 221, 90, 79, 22, 170, 18, 23, 50, 253, 71, 164, 72, 137, 157, 122, 146, 156, 248, 12, 59, 180, 41, 124, 221, 214, 58, 222, 158, 124, 221, 35, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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