← previous blocknext block →recent activity
Analyzing
Block #90,575,061
8 transactions · 7 stateful · 2026-07-26 19:59:09 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,575,061 · 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
3w04w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6fcbbb7…2b31
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x67f87cdf…e5b6
0x34b655…2a6f
4 touches
1 conflict
0x03d671f5…8003
0x34b655…2a6f
2 touches
0 conflicts
0x0bcbef25…37ed
0x34b655…2a6f
2 touches
0 conflicts
0x0ed5a116…93ee
0x34b655…2a6f
2 touches
0 conflicts
0x1074fdfa…ff79
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 0xb6fcbbb7f3…142b31
Audit this contract →
← previous block·next block →recent activity