← previous blocknext block →recent activity
Analyzing
Block #91,550,521
14 transactions · 13 stateful · 2026-07-30 05:49:49 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,550,521 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w27w38w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7bcb61d…e96f
0x34b655…2a6f
6 touches
3 conflicts
0x5b37bb6b…aaff
0x34b655…2a6f
6 touches
3 conflicts
0xcc58c80b…ff79
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x8a1e429b…f85c
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x99701186…1cbf
0x34b655…2a6f
6 touches
3 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 0xf7bcb61d4d…fde96f
Audit this contract →
← previous block·next block →recent activity