← previous blocknext block →recent activity
Analyzing
Block #105,542,530
23 transactions · 22 stateful · 2026-09-17 07:12:03 UTC
Parallelism
78/100
Blocked
45%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,542,530 · 23 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
3w04w15w06w17w28w310w011w113w014w115w016w117w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe97d54c5…ef6f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x526cad89…8615
0x34b655…2a6f
6 touches
3 conflicts
0x56755b2b…8d44
0x34b655…2a6f
6 touches
3 conflicts
0x64e296b0…cd76
0x34b655…2a6f
6 touches
3 conflicts
0x83fb1f13…53d7
0x34b655…2a6f
6 touches
3 conflicts
0xa9a49465…0424
0x34b655…2a6f
6 touches
3 conflicts
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity