← previous blocknext block →recent activity
Analyzing
Block #90,025,244
23 transactions · 18 stateful · 2026-07-24 21:33:26 UTC
Parallelism
91/100
Blocked
6%
Avg conflicts / tx
0.04
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,025,244 · 23 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
6w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02bf7faf…ca0e
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x3568fc59…2dc3
0x34b655…2a6f
4 touches
1 conflict
0x22af2208…099e
0x34b655…2a6f
2 touches
0 conflicts
0x24fe9b2d…e9b4
0x34b655…2a6f
2 touches
0 conflicts
0x4a6982a4…158c
0x34b655…2a6f
2 touches
0 conflicts
0x4c623175…29e4
0x34b655…2a6f
2 touches
0 conflicts
0x4cdf55e1…0f2d
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 0x02bf7faf1b…89ca0e
Audit this contract →
← previous block·next block →recent activity