← previous blocknext block →recent activity
Analyzing
Block #106,185,183
27 transactions · 27 stateful · 2026-09-19 13:09:01 UTC
Parallelism
74/100
Blocked
26%
Avg conflicts / tx
0.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,185,183 · 27 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
1w02w17w010w211w312w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd62f3741…b903
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x559b9b44…9024
0x34b655…2a6f
10 touches
10 conflicts
0xb2560305…f27d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
6 touches
3 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
6 touches
3 conflicts
0x56828d99…6126
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
10 conflicts on slot 0xd62f374157…55b903
Audit this contract →
← previous block·next block →recent activity