← previous blocknext block →recent activity
Analyzing
Block #106,959,568
24 transactions · 22 stateful · 2026-09-22 06:07:34 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,959,568 · 24 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
1w02w03w17w08w29w310w115w116w217w018w419w020w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9022af22…ca3c
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1c59817b…07e8
0x34b655…2a6f
6 touches
3 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0x04994ed2…9032
0x34b655…2a6f
6 touches
3 conflicts
0x6ca15e14…7be8
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 0x9022af220b…e6ca3c
Audit this contract →
← previous block·next block →recent activity