← previous blocknext block →recent activity
Analyzing
Block #99,257,279
14 transactions · 12 stateful · 2026-08-26 06:27:46 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,257,279 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41c56387…a8f6
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd36ed1d5…b4df
0x34b655…2a6f
4 touches
1 conflict
0x03fccbac…059f
0x34b655…2a6f
2 touches
0 conflicts
0x08c656a8…6568
0x34b655…2a6f
2 touches
0 conflicts
0x0b1daf3c…cae1
0x34b655…2a6f
2 touches
0 conflicts
0x171d9a84…b3b7
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 0x41c5638713…86a8f6
Audit this contract →
← previous block·next block →recent activity