← previous blocknext block →recent activity
Analyzing
Block #99,265,134
18 transactions · 16 stateful · 2026-08-26 07:07:22 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,265,134 · 18 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
1w02w03w14w05w16w110w011w112w213w214w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68dfc6ca…56ac
0x34b655…2a6f
6 touches
3 conflicts
0x76622fb2…4f08
0x34b655…2a6f
6 touches
3 conflicts
0x1f6f8ff8…a5d5
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48cce82e…5807
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
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 0x68dfc6ca63…a056ac
Audit this contract →
← previous block·next block →recent activity