← previous blocknext block →recent activity
Analyzing
Block #89,665,402
16 transactions · 13 stateful · 2026-07-23 15:19:00 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,665,402 · 16 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
13w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a2f19ef…f94e
0x34b655…2a6f
4 touches
1 conflict
0x0c33bb29…c6a9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
2 touches
0 conflicts
0x1ef3d54e…667a
0x34b655…2a6f
2 touches
0 conflicts
0x3be75497…9a3c
0x34b655…2a6f
2 touches
0 conflicts
0x3f957e98…4a58
0x34b655…2a6f
2 touches
0 conflicts
0x3fa02211…d4f6
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 0x5a2f19effd…cef94e
Audit this contract →
← previous block·next block →recent activity