← previous blocknext block →recent activity
Analyzing
Block #90,438,233
11 transactions · 11 stateful · 2026-07-26 08:30:20 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,438,233 · 11 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
3w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36a76bd2…1fb0
0x34b655…2a6f
4 touches
1 conflict
0x4332bc2b…f8c3
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0x7f3b521f…a6c8
0x34b655…2a6f
4 touches
1 conflict
0x20fbcaee…bb79
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x3b552ea8…3a4b
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
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 0x36a76bd264…b01fb0
Audit this contract →
← previous block·next block →recent activity