← previous blocknext block →recent activity
Analyzing
Block #105,851,343
21 transactions · 20 stateful · 2026-09-18 09:07:49 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,851,343 · 21 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
1w02w13w14w05w16w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xaac0f5bb…f24a
0x34b655…2a6f
14 touches
21 conflicts
0x831f75b4…945d
0x34b655…2a6f
14 touches
21 conflicts
0xe115ce3f…19c8
0x34b655…2a6f
10 touches
10 conflicts
0x932a9590…0b19
0x34b655…2a6f
8 touches
6 conflicts
0x4abfb389…18f4
0x34b655…2a6f
8 touches
6 conflicts
0x5c926c97…0436
0x34b655…2a6f
4 touches
1 conflict
0x7bf4ea6c…3cdc
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity