← previous blocknext block →recent activity
Analyzing
Block #90,553,780
8 transactions · 7 stateful · 2026-07-26 18:12:07 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,553,780 · 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02ecd54c…1f6c
0x34b655…2a6f
4 touches
1 conflict
0x793b6cb1…63c7
0x34b655…2a6f
4 touches
1 conflict
0xdb09673b…671c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x403fb46d…0d5a
0x34b655…2a6f
4 touches
1 conflict
0x403fb46d…0d5b
0x34b655…2a6f
4 touches
1 conflict
0xda728f1f…dc4b
0x34b655…2a6f
3 touches
1 conflict
0x266a2581…acaf
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 0x02ecd54c51…8f1f6c
Audit this contract →
← previous block·next block →recent activity