← previous blocknext block →recent activity
Analyzing
Block #90,025,293
10 transactions · 9 stateful · 2026-07-24 21:33:41 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,025,293 · 10 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
2w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ca37118…3c71
0x34b655…2a6f
4 touches
1 conflict
0x28f324ed…9db7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0372ca6b…c18f
0x34b655…2a6f
2 touches
0 conflicts
0x0d876411…c303
0x34b655…2a6f
2 touches
0 conflicts
0x22c8de45…2522
0x34b655…2a6f
2 touches
0 conflicts
0x2bad40ae…0522
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 0x4ca37118aa…b93c71
Audit this contract →
← previous block·next block →recent activity