← previous blocknext block →recent activity
Analyzing
Block #106,952,678
21 transactions · 20 stateful · 2026-09-22 05:32:53 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,952,678 · 21 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
2w06w08w09w112w113w115w216w317w419w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x363faadf…ea0a
0x34b655…2a6f
10 touches
10 conflicts
0xf58f6387…da5e
0x34b655…2a6f
8 touches
6 conflicts
0x70986451…c6bd
0x34b655…2a6f
8 touches
6 conflicts
0x148c2efc…4410
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x35c96674…ccb7
0x34b655…2a6f
6 touches
3 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
6 touches
3 conflicts
0xba1edffb…323e
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 0x363faadf32…5aea0a
Audit this contract →
← previous block·next block →recent activity