← previous blocknext block →recent activity
Analyzing
Block #90,204,479
8 transactions · 8 stateful · 2026-07-25 12:39:44 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,204,479 · 8 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
1w02w13w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7c09b47…3e3c
0x34b655…2a6f
6 touches
3 conflicts
0x1fd19887…8e0e
0x34b655…2a6f
4 touches
1 conflict
0x29856edf…841b
0x34b655…2a6f
4 touches
1 conflict
0x3eede796…d745
0x34b655…2a6f
4 touches
1 conflict
0x6777440a…afd6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
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 0xc7c09b4728…d03e3c
Audit this contract →
← previous block·next block →recent activity