← previous blocknext block →recent activity
Analyzing
Block #90,297,619
13 transactions · 13 stateful · 2026-07-25 20:30:14 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,297,619 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x314add6a…c880
0x34b655…2a6f
4 touches
1 conflict
0x4a6982a4…158c
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xad5b4350…79f3
0x34b655…2a6f
4 touches
1 conflict
0xeab8b522…d3e6
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x2a4568fd…f2de
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x314add6a68…d5c880
Audit this contract →
← previous block·next block →recent activity