← previous blocknext block →recent activity
Analyzing
Block #90,204,929
13 transactions · 12 stateful · 2026-07-25 12:42:01 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,204,929 · 13 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
3w05w16w27w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa01f2285…f16f
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x5af098c7…4807
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x89b4e7c1…25af
0x34b655…2a6f
4 touches
1 conflict
0x94e75040…4b0e
0x34b655…2a6f
4 touches
1 conflict
0x98aedeb3…243a
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 0xa01f228537…b8f16f
Audit this contract →
← previous block·next block →recent activity