← previous blocknext block →recent activity
Analyzing
Block #107,848,729
28 transactions · 19 stateful · 2026-09-25 08:45:29 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.11
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #107,848,729 · 28 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
1w02w16w07w110w112w213w314w415w516w617w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf75c3a6b…0568
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x960919d7…a672
0x34b655…2a6f
8 touches
6 conflicts
0xcf4be852…6986
0x34b655…2a6f
6 touches
3 conflicts
0xee757899…302b
0x34b655…2a6f
6 touches
3 conflicts
0x84739690…385a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
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 0xf75c3a6bf5…da0568
Audit this contract →
← previous block·next block →recent activity