← previous blocknext block →recent activity
Analyzing
Block #107,823,051
24 transactions · 22 stateful · 2026-09-25 06:36:14 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,823,051 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w112w013w114w215w316w417w518w620w021w122w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64275949…d698
0x34b655…2a6f
14 touches
21 conflicts
0x5d63456d…6681
0x34b655…2a6f
14 touches
21 conflicts
0x66fc0764…05fd
0x34b655…2a6f
12 touches
15 conflicts
0x3f5831e5…02b2
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x15a642a7…3b84
0x34b655…2a6f
8 touches
6 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
6 touches
3 conflicts
0x09331726…a1bf
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
21 conflicts on slot 0x6427594999…6ed698
Audit this contract →
← previous block·next block →recent activity