← previous blocknext block →recent activity
Analyzing
Block #87,303,780
21 transactions · 20 stateful · 2026-07-12 16:18:40 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,303,780 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w310w011w112w417w118w219w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa05444cf…cd70
0x34b655…2a6f
10 touches
10 conflicts
0x2484cc15…5afc
0x34b655…2a6f
6 touches
3 conflicts
0x2a3271c6…e1ec
0x34b655…2a6f
6 touches
3 conflicts
0x53bda555…3810
0x34b655…2a6f
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x79fade94…7f93
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
10 conflicts on slot 0xa05444cff4…1ecd70
Audit this contract →
← previous block·next block →recent activity