Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7426c58f7b045e6c2849802f65c5e11ecdfd7f74db18c6a3ee023fafb87e5a2

Tx prefix hash: a1413be171f2dd2724b47099120ccc6431b71c428cdecfa459700a9a01bebc3b
Tx public key: 8d175de399096fa5b1c077323f38ef5cd0b3a09c0103719e5cb3819a66b64162
Timestamp: 1719893350 Timestamp [UCT]: 2024-07-02 04:09:10 Age [y:d:h:m:s]: 00:297:05:38:32
Block: 1056665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212403 RingCT/type: yes/0
Extra: 018d175de399096fa5b1c077323f38ef5cd0b3a09c0103719e5cb3819a66b64162021100000002ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c92811a8619e92d682549f953ace5296b82cb0f85a536f3ad241e329ee254d2 0.600000000000 1527082 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": 1056675, "vin": [ { "gen": { "height": 1056665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c92811a8619e92d682549f953ace5296b82cb0f85a536f3ad241e329ee254d2" } } ], "extra": [ 1, 141, 23, 93, 227, 153, 9, 111, 165, 177, 192, 119, 50, 63, 56, 239, 92, 208, 179, 160, 156, 1, 3, 113, 158, 92, 179, 129, 154, 102, 182, 65, 98, 2, 17, 0, 0, 0, 2, 221, 211, 219, 145, 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