← previous blocknext block →recent activity
Analyzing
Block #106,190,680
22 transactions · 19 stateful · 2026-09-19 13:36:40 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,190,680 · 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
1w02w17w110w211w313w214w415w516w617w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd41f5136…97c6
0x34b655…2a6f
12 touches
15 conflicts
0xd7bbf1c1…d16d
0x34b655…2a6f
10 touches
10 conflicts
0xdfe41699…7dad
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
6 touches
3 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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 0xd41f513688…4197c6
Audit this contract →
← previous block·next block →recent activity