Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a9e56d8bb6e4b699faeb5511b8ed6a69914693d14e13a7bda0fabe0717211e7

Tx prefix hash: 8923d0185efc2f670750ba2ee902466f4aa4926dc2357d28bc4c511498d1def8
Tx public key: c3c9c9c43570699a4d9fe389750f57c9f4743b25552f233312544ec34311e333
Timestamp: 1699600301 Timestamp [UCT]: 2023-11-10 07:11:41 Age [y:d:h:m:s]: 01:074:13:35:34
Block: 888439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314660 RingCT/type: yes/0
Extra: 01c3c9c9c43570699a4d9fe389750f57c9f4743b25552f233312544ec34311e333021100000003faf35c9c000000000000000000

1 output(s) for total of 0.698606762000 dcy

stealth address amount amount idx
00: e4419d15ded4ed4f14aeaba17de616ee6515ea78fec408ca4f5d9697063bad2f 0.698606762000 1344378 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": 888449, "vin": [ { "gen": { "height": 888439 } } ], "vout": [ { "amount": 698606762, "target": { "key": "e4419d15ded4ed4f14aeaba17de616ee6515ea78fec408ca4f5d9697063bad2f" } } ], "extra": [ 1, 195, 201, 201, 196, 53, 112, 105, 154, 77, 159, 227, 137, 117, 15, 87, 201, 244, 116, 59, 37, 85, 47, 35, 51, 18, 84, 78, 195, 67, 17, 227, 51, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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