← previous blocknext block →recent activity
Analyzing
Block #105,601,113
27 transactions · 27 stateful · 2026-09-17 12:06:55 UTC
Parallelism
63/100
Blocked
59%
Avg conflicts / tx
2.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,601,113 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w59w117w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5847c4d…a65c
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x6771eae2…7014
0x34b655…2a6f
8 touches
6 conflicts
0x7923dbc4…0322
0x34b655…2a6f
8 touches
6 conflicts
0xa7002a6a…c137
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x8968fc32…20e3
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
28 conflicts on slot 0xc5847c4d32…49a65c
Audit this contract →
← previous block·next block →recent activity