← previous blocknext block →recent activity
Analyzing
Block #106,154,843
21 transactions · 21 stateful · 2026-09-19 10:36:20 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,154,843 · 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
2w03w14w15w211w013w215w116w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74eb24d4…f0c7
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
8 touches
6 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
8 touches
6 conflicts
0x6183ee9a…21b1
0x34b655…2a6f
8 touches
6 conflicts
0x8484e192…ad79
0x34b655…2a6f
8 touches
6 conflicts
0x574628e9…dcc3
0x34b655…2a6f
6 touches
3 conflicts
0x9464a960…c017
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
6 conflicts on slot 0x74eb24d4c1…e2f0c7
Audit this contract →
← previous block·next block →recent activity