← previous blocknext block →recent activity
Analyzing
Block #105,542,717
11 transactions · 11 stateful · 2026-09-17 07:13:00 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,542,717 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w28w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xe97d54c5…ef6f
0x34b655…2a6f
4 touches
1 conflict
0x6f32a04c…0e17
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x88e92ec7…696d
0x34b655…2a6f
4 touches
1 conflict
0x2249932e…474a
0x34b655…2a6f
2 touches
0 conflicts
0x2e957c13…4777
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity