← previous blocknext block →recent activity
Analyzing
Block #98,388,020
43 transactions · 27 stateful · 2026-08-23 04:51:10 UTC
Parallelism
91/100
Blocked
37%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,388,020 · 43 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w111w213w014w119w220w021w122w023w131w033w034w136w238w341w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa3996adc…4313
0x065c9d…c394
5 touches
3 conflicts
0xb4ad42a4…b935
0xd32edf…ff58
5 touches
3 conflicts
0x094c7530…e7b4
0x34b655…2a6f
4 touches
1 conflict
0x2101bec4…84b9
0x34b655…2a6f
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity