← previous blocknext block →recent activity
Analyzing
Block #106,944,618
27 transactions · 21 stateful · 2026-09-22 04:52:19 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,944,618 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w017w019w020w123w125w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1643e0fb…7385
0x34b655…2a6f
8 touches
6 conflicts
0x7462b8f2…6312
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x704a8131…bbe8
0x34b655…2a6f
8 touches
6 conflicts
0x71d9fed1…4988
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x261cbea7…e35d
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 0x1643e0fbc5…907385
Audit this contract →
← previous block·next block →recent activity