← previous blocknext block →recent activity
Analyzing
Block #98,658,153
19 transactions · 14 stateful · 2026-08-24 03:59:35 UTC
Parallelism
84/100
Blocked
36%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,658,153 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w111w112w214w016w017w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0xdbaaf2a4…71d2
0xd32edf…ff58
3 touches
1 conflict
0x7aa91b8f…d070
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6a9d
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6aa2
0x2b46c0…1669
2 touches
0 conflicts
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: Perpl
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity