Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c2bb7fd8e5db6c3dc08909617f1d82713d6be72c97444827b562b24b1acc6a8

Tx prefix hash: 0a02e8b2c56de56c92b0920a4ec7a4a68ef0979173a48343e489b1c29f6b751c
Tx public key: 66048ad6cdd43b18177f706e24b2c6cce35d7e464f9a763149d5bfbb20a496f6
Timestamp: 1685868292 Timestamp [UCT]: 2023-06-04 08:44:52 Age [y:d:h:m:s]: 01:306:18:10:34
Block: 774828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480435 RingCT/type: yes/0
Extra: 0166048ad6cdd43b18177f706e24b2c6cce35d7e464f9a763149d5bfbb20a496f602110000000433af99f4000000000000000000

1 output(s) for total of 1.662162027000 dcy

stealth address amount amount idx
00: abd3b84051394f69b89296a8a1bfb3b3b2efa402352f97e2ca7e604ecd3ab1c9 1.662162027000 1224315 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": 774838, "vin": [ { "gen": { "height": 774828 } } ], "vout": [ { "amount": 1662162027, "target": { "key": "abd3b84051394f69b89296a8a1bfb3b3b2efa402352f97e2ca7e604ecd3ab1c9" } } ], "extra": [ 1, 102, 4, 138, 214, 205, 212, 59, 24, 23, 127, 112, 110, 36, 178, 198, 204, 227, 93, 126, 70, 79, 154, 118, 49, 73, 213, 191, 187, 32, 164, 150, 246, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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