← previous blocknext block →recent activity
Analyzing
Block #98,663,133
20 transactions · 20 stateful · 2026-08-24 04:25:35 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,663,133 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x11b69a7e…334e
0xee8c0e…1242
8 touches
6 conflicts
0x98a278f4…ddf4
0xa6afd3…d132
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: MarginAccount
10 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity