← previous blocknext block →recent activity
Analyzing
Block #106,934,087
21 transactions · 21 stateful · 2026-09-22 03:59:18 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,934,087 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w18w19w213w114w315w416w519w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x469dac8d…3411
0x34b655…2a6f
10 touches
10 conflicts
0x6aadac07…372a
0x34b655…2a6f
10 touches
10 conflicts
0x2b10fdcf…13db
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0x6d6c8b37…a8cd
0x34b655…2a6f
6 touches
3 conflicts
0x34c48330…703f
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
10 conflicts on slot 0x469dac8dcd…223411
Audit this contract →
← previous block·next block →recent activity