← previous blocknext block →recent activity
Analyzing
Block #90,573,532
8 transactions · 7 stateful · 2026-07-26 19:51:27 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,573,532 · 8 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x3c1149e2…de31
0x34b655…2a6f
4 touches
1 conflict
0x149af613…d62e
0x34b655…2a6f
2 touches
0 conflicts
0x4c188934…158e
0x34b655…2a6f
2 touches
0 conflicts
0x9c166a56…0356
0x34b655…2a6f
2 touches
0 conflicts
0xc3a8e1d6…e816
0x34b655…2a6f
2 touches
0 conflicts
0xe5ddbbc9…91a7
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 0xa3ed5a0966…25c6d3
Audit this contract →
← previous block·next block →recent activity