← previous blocknext block →recent activity
Analyzing
Block #98,473,429
22 transactions · 22 stateful · 2026-08-23 12:01:14 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,473,429 · 22 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
1w04w05w18w09w110w211w314w017w120w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d564c82…b3f1
0x34b655…2a6f
6 touches
3 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
6 touches
3 conflicts
0x67c69db9…7906
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x5a95f394…be66
0x34b655…2a6f
4 touches
1 conflict
0x5d6da397…6c5c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a3
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
3 conflicts on slot 0x7d564c8280…0db3f1
Audit this contract →
← previous block·next block →recent activity