← previous blocknext block →recent activity
Analyzing
Block #89,738,987
12 transactions · 11 stateful · 2026-07-23 21:31:01 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,738,987 · 12 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
10w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa68dfacc…cdb8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x923c57f1…7810
0x34b655…2a6f
4 touches
1 conflict
0x2e4e7336…e906
0x34b655…2a6f
2 touches
0 conflicts
0x4a2773bc…e7b4
0x34b655…2a6f
2 touches
0 conflicts
0x4de03fa6…fe72
0x34b655…2a6f
2 touches
0 conflicts
0x4deeee1b…8c0c
0x34b655…2a6f
2 touches
0 conflicts
0x5a65207b…4f30
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 0xa68dfacc6a…72cdb8
Audit this contract →
← previous block·next block →recent activity