← previous blocknext block →recent activity
Analyzing
Block #107,816,637
17 transactions · 15 stateful · 2026-09-25 06:03:57 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
1.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,816,637 · 17 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
1w02w16w07w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4d55d…c588
0x34b655…2a6f
14 touches
21 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
12 touches
15 conflicts
0xae8bf21e…cd46
0x34b655…2a6f
10 touches
10 conflicts
0xf9249950…fee6
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x43e3decb…be40
0x34b655…2a6f
8 touches
6 conflicts
0x44b4869a…fe59
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
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 0x5cf4d55d39…13c588
Audit this contract →
← previous block·next block →recent activity