← previous blocknext block →recent activity
Analyzing
Block #106,951,770
24 transactions · 24 stateful · 2026-09-22 05:28:19 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,951,770 · 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
1w02w14w05w06w19w010w111w212w113w314w418w219w320w422w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7489f363…146d
0x34b655…2a6f
10 touches
10 conflicts
0xa9988419…9f45
0x34b655…2a6f
8 touches
6 conflicts
0xab41643c…f9bf
0x34b655…2a6f
8 touches
6 conflicts
0x94e7f277…471b
0x34b655…2a6f
8 touches
6 conflicts
0x8590b692…b267
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0x777ad478…c120
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 0x7489f363a6…e6146d
Audit this contract →
← previous block·next block →recent activity