Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58e837ee2037e296fe33c843f6003ece72fa134497e6c0b276d66e374d6860cd

Tx prefix hash: cf3f254debd4d42ab5c71c290a20e0fdc4f9f2ffb447fd3ba799f963fe7f0036
Tx public key: 7234bb2c78bf17cd2b21893ce1725fbd5a1d48791c096372e44b88b589fcd0b1
Timestamp: 1708334396 Timestamp [UCT]: 2024-02-19 09:19:56 Age [y:d:h:m:s]: 01:259:18:40:04
Block: 960842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444397 RingCT/type: yes/0
Extra: 017234bb2c78bf17cd2b21893ce1725fbd5a1d48791c096372e44b88b589fcd0b102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e03694225c60bc8794efda5e1d93d08ee8cdc65ed356823e0f8504c0f7434a8d 0.600000000000 1420429 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": 960852, "vin": [ { "gen": { "height": 960842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e03694225c60bc8794efda5e1d93d08ee8cdc65ed356823e0f8504c0f7434a8d" } } ], "extra": [ 1, 114, 52, 187, 44, 120, 191, 23, 205, 43, 33, 137, 60, 225, 114, 95, 189, 90, 29, 72, 121, 28, 9, 99, 114, 228, 75, 136, 181, 137, 252, 208, 177, 2, 17, 0, 0, 0, 2, 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