← previous blocknext block →recent activity
Analyzing
Block #89,527,413
13 transactions · 13 stateful · 2026-07-23 00:11:23 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,527,413 · 13 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ebf04a8…42e6
0x34b655…2a6f
4 touches
1 conflict
0x5f2c121e…8f3c
0x34b655…2a6f
4 touches
1 conflict
0x5f2c121e…8f3d
0x34b655…2a6f
4 touches
1 conflict
0xe8058ec4…ebac
0x34b655…2a6f
4 touches
1 conflict
0x09178a69…7ef2
0x34b655…2a6f
4 touches
1 conflict
0x177286e0…be71
0x34b655…2a6f
4 touches
1 conflict
0x394692f4…8926
0x34b655…2a6f
4 touches
1 conflict
0xba5743c7…21c0
0x1b6862…e19c
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 0x4ebf04a882…9a42e6
Audit this contract →
← previous block·next block →recent activity