← previous blocknext block →recent activity
Analyzing
Block #106,424,400
12 transactions · 11 stateful · 2026-09-20 09:12:58 UTC
Parallelism
58/100
Blocked
64%
Avg conflicts / tx
1.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,424,400 · 12 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
1w02w13w24w05w17w18w29w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05fc2bb7…c2c2
0x34b655…2a6f
8 touches
6 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
8 touches
6 conflicts
0x5a55a9d1…e7ce
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x93afca4c…b47b
0x1b6862…e19c
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
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
6 conflicts on slot 0x05fc2bb7ca…43c2c2
Audit this contract →
← previous block·next block →recent activity