← previous blocknext block →recent activity
Analyzing
Block #106,367,240
14 transactions · 14 stateful · 2026-09-20 04:25:18 UTC
Parallelism
57/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,367,240 · 14 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
2w03w14w25w36w47w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe62b807…03da
0x34b655…2a6f
8 touches
6 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
8 touches
6 conflicts
0xdd77da90…6df4
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xf6d2da5f…9e78
0x34b655…2a6f
4 touches
1 conflict
0x0307261f…c2d2
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
6 conflicts on slot 0xbe62b8076b…1c03da
Audit this contract →
← previous block·next block →recent activity