← previous blocknext block →recent activity
Analyzing
Block #105,853,133
22 transactions · 22 stateful · 2026-09-18 09:16:50 UTC
Parallelism
77/100
Blocked
41%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,853,133 · 22 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
1w06w07w18w214w315w216w317w318w420w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f1d8ea3…03ae
0x34b655…2a6f
8 touches
6 conflicts
0xe115ce3f…19c8
0x34b655…2a6f
8 touches
6 conflicts
0x18978822…2623
0x34b655…2a6f
6 touches
3 conflicts
0x831f75b4…945d
0x34b655…2a6f
6 touches
3 conflicts
0xd79c9727…1233
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x5941ba6d…8ced
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
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
6 conflicts on slot 0x4f1d8ea3be…5b03ae
Audit this contract →
← previous block·next block →recent activity