← previous blocknext block →recent activity
Analyzing
Block #107,814,834
21 transactions · 21 stateful · 2026-09-25 05:54:53 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,814,834 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w18w29w310w411w312w413w515w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1665d211…9e2d
0x34b655…2a6f
12 touches
15 conflicts
0x740fff9f…4244
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xa38c430a…e3cb
0x34b655…2a6f
8 touches
6 conflicts
0xe79b20f3…b736
0x34b655…2a6f
8 touches
6 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
6 touches
3 conflicts
0xaddcd70c…c4d6
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 0x1665d211b2…5d9e2d
Audit this contract →
← previous block·next block →recent activity