← previous blocknext block →recent activity
Analyzing
Block #105,851,128
22 transactions · 21 stateful · 2026-09-18 09:06:44 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,851,128 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w08w110w011w114w215w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x4ade270b…14fb
0x34b655…2a6f
12 touches
15 conflicts
0x6caf33e2…c261
0x34b655…2a6f
12 touches
15 conflicts
0x932a9590…0b19
0x34b655…2a6f
10 touches
10 conflicts
0x548d7934…235a
0x34b655…2a6f
10 touches
10 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
8 touches
6 conflicts
0x1afd1723…2a45
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity