← previous blocknext block →recent activity
Analyzing
Block #105,855,883
31 transactions · 30 stateful · 2026-09-18 09:30:41 UTC
Parallelism
65/100
Blocked
67%
Avg conflicts / tx
2.19
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,855,883 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w18w211w215w316w218w419w520w621w722w823w924w1030w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8e6479f…f193
0x34b655…2a6f
18 touches
36 conflicts
0x29fc3fce…1d6e
0x34b655…2a6f
16 touches
28 conflicts
0x4118bd12…924a
0x34b655…2a6f
12 touches
15 conflicts
0xfefb0189…f726
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
36 conflicts on slot 0xf8e6479f3b…bbf193
Audit this contract →
← previous block·next block →recent activity