← previous blocknext block →recent activity
Analyzing
Block #105,845,507
28 transactions · 28 stateful · 2026-09-18 08:38:27 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.93
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,845,507 · 28 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
2w03w14w15w28w219w320w421w523w624w725w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeee61405…7284
0x34b655…2a6f
14 touches
21 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x941bd594…21fd
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
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
21 conflicts on slot 0xeee614053d…5d7284
Audit this contract →
← previous block·next block →recent activity