← previous blocknext block →recent activity
Analyzing
Block #99,614,733
35 transactions · 22 stateful · 2026-08-27 12:32:59 UTC
Parallelism
89/100
Blocked
32%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,614,733 · 35 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
1w05w06w07w18w114w125w027w231w232w334w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32e50ec9…0a65
0x34b655…2a6f
6 touches
3 conflicts
0x931975c2…b7b3
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x3c9b10c1…d791
0x34b655…2a6f
6 touches
3 conflicts
0xe188ad90…d23f
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x26471102…35f9
0x34b655…2a6f
4 touches
1 conflict
0x33c321d6…b941
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 0x32e50ec90f…240a65
Audit this contract →
← previous block·next block →recent activity