← previous blocknext block →recent activity
Analyzing
Block #105,549,292
18 transactions · 15 stateful · 2026-09-17 07:46:05 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,549,292 · 18 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
6w08w110w113w216w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xcf11cf1a…ec04
0x34b655…2a6f
6 touches
3 conflicts
0x1bf239bd…46ad
0x34b655…2a6f
6 touches
3 conflicts
0x56755b2b…8d44
0x34b655…2a6f
4 touches
1 conflict
0xa696c8d3…535b
0x34b655…2a6f
4 touches
1 conflict
0xa9a49465…0424
0x34b655…2a6f
4 touches
1 conflict
0xae522ec4…d1e5
0x34b655…2a6f
4 touches
1 conflict
0xc08af837…3db6
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity