← previous blocknext block →recent activity
Analyzing
Block #105,843,164
27 transactions · 26 stateful · 2026-09-18 08:26:36 UTC
Parallelism
70/100
Blocked
65%
Avg conflicts / tx
2.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,843,164 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w07w18w19w210w311w412w513w614w723w225w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfce7dfe…5053
0x34b655…2a6f
16 touches
28 conflicts
0x0a6862d7…c311
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xff7cb355…3404
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 0xdfce7dfe53…c75053
Audit this contract →
← previous block·next block →recent activity