← previous blocknext block →recent activity
Analyzing
Block #106,185,246
17 transactions · 15 stateful · 2026-09-19 13:09:20 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,185,246 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w110w211w314w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56409df0…27cd
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc44003b5…2dac
0x34b655…2a6f
6 touches
3 conflicts
0xb550abea…2729
0x34b655…2a6f
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfadc118d…5d64
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
6 conflicts on slot 0x56409df050…ad27cd
Audit this contract →
← previous block·next block →recent activity