← previous blocknext block →recent activity
Analyzing
Block #90,026,168
18 transactions · 16 stateful · 2026-07-24 21:38:05 UTC
Parallelism
61/100
Blocked
44%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,026,168 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w514w015w616w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0x4bc1abab…5874
0x34b655…2a6f
12 touches
15 conflicts
0xbfb9e90e…d36c
0x34b655…2a6f
9 touches
10 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0x6ba1eca0…e96f
0x34b655…2a6f
5 touches
3 conflicts
0xd7f16d2a…c01b
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
21 conflicts on slot 0xf3d10975b0…050d07
Audit this contract →
← previous block·next block →recent activity