← previous blocknext block →recent activity
Analyzing
Block #107,813,136
27 transactions · 24 stateful · 2026-09-25 05:46:20 UTC
Parallelism
70/100
Blocked
54%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,813,136 · 27 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
2w03w18w210w012w013w114w315w417w118w220w221w322w423w524w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
8 touches
6 conflicts
0x85473e46…670e
0x34b655…2a6f
8 touches
6 conflicts
0x03c639f9…fb2d
0x34b655…2a6f
6 touches
3 conflicts
0xba522812…1f1f
0x34b655…2a6f
6 touches
3 conflicts
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity