← previous blocknext block →recent activity
Analyzing
Block #87,331,509
16 transactions · 15 stateful · 2026-07-12 19:24:07 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,331,509 · 16 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
1w03w04w05w16w29w110w211w312w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eef368f…aa21
0x34b655…2a6f
6 touches
3 conflicts
0xc0124edf…7d30
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x5417efb2…442c
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x63b15849…80b2
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
3 conflicts on slot 0x8eef368f1b…01aa21
Audit this contract →
← previous block·next block →recent activity