← previous blocknext block →recent activity
Analyzing
Block #107,817,212
26 transactions · 26 stateful · 2026-09-25 06:06:51 UTC
Parallelism
62/100
Blocked
58%
Avg conflicts / tx
1.69
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #107,817,212 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w18w29w313w314w415w516w517w618w619w720w722w824w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
14 touches
21 conflicts
0x788154ed…9aa3
0x34b655…2a6f
10 touches
10 conflicts
0x2b856d86…7988
0x34b655…2a6f
10 touches
10 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
8 touches
6 conflicts
0x438b9fc3…386b
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x5cf4d55d…c588
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity