← previous blocknext block →recent activity
Analyzing
Block #105,855,961
13 transactions · 13 stateful · 2026-09-18 09:31:04 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,855,961 · 13 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
1w02w15w26w07w38w412w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa27ff98e…994a
0x34b655…2a6f
6 touches
3 conflicts
0x33416595…47c0
0x34b655…2a6f
6 touches
3 conflicts
0x297de2d5…7396
0x34b655…2a6f
6 touches
3 conflicts
0xf8e6479f…f193
0x34b655…2a6f
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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
3 conflicts on slot 0xa27ff98e82…53994a
Audit this contract →
← previous block·next block →recent activity