Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 602efc075760b34cf4ae3d64b5f2b2b8c4fa4ad98c9c5ebc69f026fc6aa63ff5

Tx prefix hash: 4cbcbdf931b8de959c8558e478c260039dbdc15d8bac586603fbfe80039e3731
Tx public key: 9f9ddbcc95c17d2547f24d19caa2b52c6da6c338279d74772505207561b8cbbf
Timestamp: 1713723742 Timestamp [UCT]: 2024-04-21 18:22:22 Age [y:d:h:m:s]: 01:192:12:40:02
Block: 1005513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396254 RingCT/type: yes/0
Extra: 019f9ddbcc95c17d2547f24d19caa2b52c6da6c338279d74772505207561b8cbbf0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4e2f580ba098508ef1a354e554291dc6d4ce72664661392f6d6bed1d11766ba 0.600000000000 1466231 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": 1005523, "vin": [ { "gen": { "height": 1005513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4e2f580ba098508ef1a354e554291dc6d4ce72664661392f6d6bed1d11766ba" } } ], "extra": [ 1, 159, 157, 219, 204, 149, 193, 125, 37, 71, 242, 77, 25, 202, 162, 181, 44, 109, 166, 195, 56, 39, 157, 116, 119, 37, 5, 32, 117, 97, 184, 203, 191, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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