← previous blocknext block →recent activity
Analyzing
Block #99,879,297
23 transactions · 23 stateful · 2026-08-28 10:52:11 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,879,297 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w28w39w410w514w115w016w117w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59b6f111…8095
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xc16e646d…4fb0
0x34b655…2a6f
6 touches
3 conflicts
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x52cf5603…ca01
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
10 conflicts on slot 0x59b6f111d2…6a8095
Audit this contract →
← previous block·next block →recent activity