← previous blocknext block →recent activity
Analyzing
Block #89,402,374
10 transactions · 9 stateful · 2026-07-22 10:15:53 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,402,374 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bfc7921…ffc8
0x34b655…2a6f
6 touches
3 conflicts
0x6fbd5ec9…7fb4
0x34b655…2a6f
4 touches
1 conflict
0x9a274419…bfb8
0x34b655…2a6f
4 touches
1 conflict
0xef3f5637…f47c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xc8179a56…1039
0xe52b14…7230
3 touches
1 conflict
0x304a552a…8fc7
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
3 conflicts on slot 0x6bfc7921dc…a4ffc8
Audit this contract →
← previous block·next block →recent activity