← previous blocknext block →recent activity
Analyzing
Block #107,823,254
21 transactions · 21 stateful · 2026-09-25 06:37:16 UTC
Parallelism
62/100
Blocked
52%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,823,254 · 21 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
5w06w07w18w29w310w411w412w513w614w715w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xa7ba83b5…d0a8
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xf865ea42…25bb
0x34b655…2a6f
8 touches
6 conflicts
0x25144f94…1854
0x34b655…2a6f
8 touches
6 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
6 touches
3 conflicts
0x3750b746…5a9e
0x34b655…2a6f
6 touches
3 conflicts
0xba9f9225…2ead
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
10 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity