← previous blocknext block →recent activity
Analyzing
Block #99,187,301
26 transactions · 26 stateful · 2026-08-26 00:35:41 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
1.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,187,301 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w18w29w311w013w015w116w217w018w119w320w423w524w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f52f2b3…8208
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x34183e80…92a4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x168cce20…53ee
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x7f52f2b39f…d38208
Audit this contract →
← previous block·next block →recent activity