← previous blocknext block →recent activity
Analyzing
Block #90,800,917
15 transactions · 14 stateful · 2026-07-27 14:55:24 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,800,917 · 15 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
4w05w16w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9022fabe…5862
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x05ae5149…f967
0x34b655…2a6f
2 touches
0 conflicts
0x13510de3…1c68
0x34b655…2a6f
2 touches
0 conflicts
0x1bee5aea…5f61
0x34b655…2a6f
2 touches
0 conflicts
0x42203cbd…4857
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 0x9022fabe6b…e45862
Audit this contract →
← previous block·next block →recent activity