← previous blocknext block →recent activity
Analyzing
Block #107,816,434
22 transactions · 16 stateful · 2026-09-25 06:02:56 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,816,434 · 22 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
5w06w17w28w39w410w511w613w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe098738f…9bbe
0x34b655…2a6f
12 touches
15 conflicts
0xaa97569b…1480
0x34b655…2a6f
12 touches
15 conflicts
0xbdd97c21…e3d0
0x34b655…2a6f
10 touches
10 conflicts
0xc4c059d8…185d
0x34b655…2a6f
8 touches
6 conflicts
0xc10b903d…2f54
0x34b655…2a6f
8 touches
6 conflicts
0x693badd1…0fa5
0x34b655…2a6f
6 touches
3 conflicts
0xb6039eff…b0d1
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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
15 conflicts on slot 0xe098738f16…fd9bbe
Audit this contract →
← previous block·next block →recent activity