← previous blocknext block →recent activity
Analyzing
Block #107,823,008
20 transactions · 17 stateful · 2026-09-25 06:36:01 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,823,008 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w210w311w412w015w016w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fc0764…05fd
0x34b655…2a6f
10 touches
10 conflicts
0x2abd107b…af15
0x34b655…2a6f
10 touches
10 conflicts
0x09331726…a1bf
0x34b655…2a6f
6 touches
3 conflicts
0x64275949…d698
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x3f5831e5…02b2
0x34b655…2a6f
6 touches
3 conflicts
0x3a663e9a…a9c8
0x508254…98bd
4 touches
1 conflict
0x15a642a7…3b84
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 0x66fc076467…c305fd
Audit this contract →
← previous block·next block →recent activity