← previous blocknext block →recent activity
Analyzing
Block #106,110,301
19 transactions · 19 stateful · 2026-09-19 06:52:09 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,110,301 · 19 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
1w02w13w14w27w28w39w410w512w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc7e6c9…04c2
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x4c2ea9d0…2aca
0x34b655…2a6f
8 touches
6 conflicts
0x61e027f2…b379
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
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
6 conflicts on slot 0xdfc7e6c987…4704c2
Audit this contract →
← previous block·next block →recent activity