← previous blocknext block →recent activity
Analyzing
Block #99,876,222
17 transactions · 14 stateful · 2026-08-28 10:36:41 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,876,222 · 17 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
1w07w010w011w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdd6538fb…2b3f
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x2999ebda…ce6c
0x34b655…2a6f
2 touches
0 conflicts
0x54b965f1…42c9
0x34b655…2a6f
2 touches
0 conflicts
0x57267d66…dda6
0x34b655…2a6f
2 touches
0 conflicts
0x593a6b8f…4e8f
0x34b655…2a6f
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