← previous blocknext block →recent activity
Analyzing
Block #90,699,500
18 transactions · 16 stateful · 2026-07-27 06:25:11 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,699,500 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w07w08w19w110w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66e2720b…f019
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0e91dab0…e1b2
0xa6afd3…d132
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x921a58d1…db22
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
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
3 conflicts on slot 0x66e2720be2…14f019
Audit this contract →
← previous block·next block →recent activity