← previous blocknext block →recent activity
Analyzing
Block #107,816,170
20 transactions · 18 stateful · 2026-09-25 06:01:36 UTC
Parallelism
55/100
Blocked
56%
Avg conflicts / tx
1.4
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #107,816,170 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w28w39w411w512w613w714w815w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xc653f5c4…56e9
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xbdd97c21…e3d0
0x34b655…2a6f
6 touches
3 conflicts
0x2328941c…84d3
0x34b655…2a6f
6 touches
3 conflicts
0x3e6d4a39…5dfb
0x34b655…2a6f
6 touches
3 conflicts
0x3ea25e92…a36d
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 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity