← previous blocknext block →recent activity
Analyzing
Block #105,748,950
20 transactions · 20 stateful · 2026-09-18 00:31:04 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,748,950 · 20 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
2w03w04w15w28w39w012w413w514w618w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1373b9e…ba19
0x34b655…2a6f
14 touches
21 conflicts
0x213b816c…a5e0
0x34b655…2a6f
12 touches
15 conflicts
0x43e3decb…be40
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xdaf02dea…dbd8
0x34b655…2a6f
4 touches
1 conflict
0x166cd7f7…2b93
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
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 0xd1373b9ef5…c2ba19
Audit this contract →
← previous block·next block →recent activity