← previous blocknext block →recent activity
Analyzing
Block #106,935,759
17 transactions · 16 stateful · 2026-09-22 04:07:43 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,935,759 · 17 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
1w06w08w19w110w211w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x834f2fbe…e576
0x34b655…2a6f
10 touches
10 conflicts
0xf7b76d2f…1b9c
0x34b655…2a6f
6 touches
3 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
6 touches
3 conflicts
0x469dac8d…3411
0x34b655…2a6f
6 touches
3 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0x834f2fbedf…4fe576
Audit this contract →
← previous block·next block →recent activity