Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90fcf457db9e89dc948dd2ff32d2959a490f59163fbc67b593968dd1b03643d0

Tx prefix hash: 30c5b2b9a5ccae8019c0b92ad1eeaeedb8c5f8378d27f83694f461399df22fdb
Tx public key: 2b6cf990109edd2d2a3ac3ecff6982dc4488a7a8a128ed8450ed13bfa9859861
Timestamp: 1711650330 Timestamp [UCT]: 2024-03-28 18:25:30 Age [y:d:h:m:s]: 01:224:07:50:38
Block: 988351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418991 RingCT/type: yes/0
Extra: 012b6cf990109edd2d2a3ac3ecff6982dc4488a7a8a128ed8450ed13bfa98598610211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e827ca9110424c1475d6d24a3b3de54bd2f4bb8fa6e2704dfc9f3b8d0e826f83 0.600000000000 1448628 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": 988361, "vin": [ { "gen": { "height": 988351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e827ca9110424c1475d6d24a3b3de54bd2f4bb8fa6e2704dfc9f3b8d0e826f83" } } ], "extra": [ 1, 43, 108, 249, 144, 16, 158, 221, 45, 42, 58, 195, 236, 255, 105, 130, 220, 68, 136, 167, 168, 161, 40, 237, 132, 80, 237, 19, 191, 169, 133, 152, 97, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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