← previous blocknext block →recent activity
Analyzing
Block #106,207,189
18 transactions · 18 stateful · 2026-09-19 14:59:48 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,207,189 · 18 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
1w02w03w14w25w311w212w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaef82336…d052
0x34b655…2a6f
8 touches
6 conflicts
0x82ecfca0…d301
0x34b655…2a6f
8 touches
6 conflicts
0xbeedaa05…9eda
0x34b655…2a6f
6 touches
3 conflicts
0x315e07b8…9823
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xfefb0189…f726
0x34b655…2a6f
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 0xaef82336ed…b7d052
Audit this contract →
← previous block·next block →recent activity