← previous blocknext block →recent activity
Analyzing
Block #90,543,033
6 transactions · 6 stateful · 2026-07-26 17:18:03 UTC
Parallelism
50/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,543,033 · 6 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65f36c20…81a4
0x34b655…2a6f
6 touches
3 conflicts
0x5666db7d…5dc4
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe74deb99…9e5b
0x34b655…2a6f
4 touches
1 conflict
0x60f63d67…5ba0
0x34b655…2a6f
4 touches
1 conflict
0x42b10c57…3ee7
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
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
3 conflicts on slot 0x65f36c20fd…9281a4
Audit this contract →
← previous block·next block →recent activity