← previous blocknext block →recent activity
Analyzing
Block #105,841,851
17 transactions · 13 stateful · 2026-09-18 08:19:55 UTC
Parallelism
65/100
Blocked
54%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,841,851 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w310w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec2a8d79…70cb
0x34b655…2a6f
10 touches
10 conflicts
0x5684aadd…8d62
0x34b655…2a6f
8 touches
6 conflicts
0x5871b087…587d
0x34b655…2a6f
8 touches
6 conflicts
0xc10b903d…2f54
0x34b655…2a6f
8 touches
6 conflicts
0x3c0e1ae4…59f1
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xf90c6521…d8f0
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
10 conflicts on slot 0xec2a8d79c6…1070cb
Audit this contract →
← previous block·next block →recent activity