← previous blocknext block →recent activity
Analyzing
Block #90,544,442
5 transactions · 5 stateful · 2026-07-26 17:25:08 UTC
Parallelism
40/100
Blocked
40%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,544,442 · 5 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
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x34d4ef1a…0345
0x34b655…2a6f
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x17b720f5…ad7a
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x158becdc…73ed
0x34b655…2a6f
2 touches
0 conflicts
0x2d6392f9…f781
0x34b655…2a6f
2 touches
0 conflicts
0x41dc2b7f…1af1
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity