← previous blocknext block →recent activity
Analyzing
Block #87,490,083
24 transactions · 15 stateful · 2026-07-13 13:04:31 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,490,083 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w39w411w516w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cb4b659…f735
0x34b655…2a6f
8 touches
6 conflicts
0xc57b566d…8591
0x34b655…2a6f
6 touches
3 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0x9365e097…ff56
0x34b655…2a6f
6 touches
3 conflicts
0x4dc6cd61…f674
0x34b655…2a6f
6 touches
3 conflicts
0x56b580bf…f969
0x34b655…2a6f
4 touches
1 conflict
0x5b33f5b9…4bab
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x3cb4b65990…53f735
Audit this contract →
← previous block·next block →recent activity