← previous blocknext block →recent activity
Analyzing
Block #87,303,905
15 transactions · 13 stateful · 2026-07-12 16:19:30 UTC
Parallelism
67/100
Blocked
62%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,303,905 · 15 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
1w02w13w04w05w17w18w29w210w311w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa05444cf…cd70
0x34b655…2a6f
8 touches
6 conflicts
0xc8795659…546a
0x34b655…2a6f
6 touches
3 conflicts
0x974c36fe…1cd7
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x37ee30c9…9e70
0x34b655…2a6f
6 touches
3 conflicts
0x79ad9283…5fd1
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
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 0xa05444cff4…1ecd70
Audit this contract →
← previous block·next block →recent activity