← previous blocknext block →recent activity
Analyzing
Block #89,388,329
19 transactions · 18 stateful · 2026-07-22 08:41:58 UTC
Parallelism
84/100
Blocked
17%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,388,329 · 19 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
4w06w07w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27a1ba72…020d
0x34b655…2a6f
4 touches
1 conflict
0x255ba9f3…396d
0x34b655…2a6f
4 touches
1 conflict
0x27a1ba72…020c
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x061f1247…03fd
0x34b655…2a6f
2 touches
0 conflicts
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x31519d10…f76b
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 0x27a1ba72f2…d0020d
Audit this contract →
← previous block·next block →recent activity