← previous blocknext block →recent activity
Analyzing
Block #105,843,902
31 transactions · 30 stateful · 2026-09-18 08:30:21 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
1.32
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,843,902 · 31 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w29w010w111w012w313w414w515w616w717w829w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a548af5…0eb0
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xc693f151…3ed9
0x34b655…2a6f
12 touches
15 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0x3aed8a17…20f9
0x34b655…2a6f
10 touches
10 conflicts
0xfefb0189…f726
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x4118bd12…924a
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
36 conflicts on slot 0x5a548af508…f00eb0
Audit this contract →
← previous block·next block →recent activity