← previous blocknext block →recent activity
Analyzing
Block #98,204,249
20 transactions · 17 stateful · 2026-08-22 13:26:36 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,204,249 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w18w211w312w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5f215e1…1bb7
0x34b655…2a6f
8 touches
6 conflicts
0xaf30c163…0fb6
0x34b655…2a6f
6 touches
3 conflicts
0xaa42dd7d…6745
0x34b655…2a6f
6 touches
3 conflicts
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0xd6113c0f…0a4b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x46ee3c65…4ab8
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 0xe5f215e142…c71bb7
Audit this contract →
← previous block·next block →recent activity