← previous blocknext block →recent activity
Analyzing
Block #107,849,600
22 transactions · 21 stateful · 2026-09-25 08:49:52 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.45
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,849,600 · 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
4w05w17w08w19w210w311w412w513w617w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ae03ff2…30fd
0x34b655…2a6f
14 touches
21 conflicts
0xba522812…1f1f
0x34b655…2a6f
14 touches
21 conflicts
0xab41643c…f9bf
0x34b655…2a6f
12 touches
15 conflicts
0x8d5fc820…1750
0x34b655…2a6f
10 touches
10 conflicts
0xe8df074d…09fa
0xd32edf…ff58
9 touches
10 conflicts
0x570bf5da…6a77
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xa0cbbfcc…3133
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 0x1ae03ff2fc…9a30fd
Audit this contract →
← previous block·next block →recent activity