← previous blocknext block →recent activity
Analyzing
Block #105,856,520
20 transactions · 19 stateful · 2026-09-18 09:33:53 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,856,520 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w115w316w017w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc10b903d…2f54
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x92b49f44…ee4f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb2174c69…2504
0x34b655…2a6f
4 touches
1 conflict
0xea79e6d3…68ad
0x34b655…2a6f
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
3 conflicts on slot 0xc10b903def…412f54
Audit this contract →
← previous block·next block →recent activity