Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 228909f0f5a9918ce50cae87fcc907dddfe514893d5c70a0887f57a3ce210477

Tx prefix hash: 54d1014ce7192db296f6b9eec85d7621ba406f18a5c5a6b6255b8be26e7e17cd
Tx public key: bf958c318a20354156340a8f8fe63dc77d5779567464cefb06a9c51d8b2180b3
Timestamp: 1708683871 Timestamp [UCT]: 2024-02-23 10:24:31 Age [y:d:h:m:s]: 01:259:13:05:36
Block: 963741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444231 RingCT/type: yes/0
Extra: 01bf958c318a20354156340a8f8fe63dc77d5779567464cefb06a9c51d8b2180b302110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5269b8ad6de83cc8d4c29a79b17666a69103a5bc6c87e73bcd00e94c3a67b72b 0.600000000000 1423466 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": 963751, "vin": [ { "gen": { "height": 963741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5269b8ad6de83cc8d4c29a79b17666a69103a5bc6c87e73bcd00e94c3a67b72b" } } ], "extra": [ 1, 191, 149, 140, 49, 138, 32, 53, 65, 86, 52, 10, 143, 143, 230, 61, 199, 125, 87, 121, 86, 116, 100, 206, 251, 6, 169, 197, 29, 139, 33, 128, 179, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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