← previous blocknext block →recent activity
Analyzing
Block #87,258,871
13 transactions · 12 stateful · 2026-07-12 11:18:27 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,258,871 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w08w19w210w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c11df38…2f2c
0x34b655…2a6f
6 touches
3 conflicts
0xaedc3dd6…3c3b
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x3c6877a1…b718
0x34b655…2a6f
4 touches
1 conflict
0x5e67d94d…2dff
0x34b655…2a6f
4 touches
1 conflict
0x650e90b3…213c
0x34b655…2a6f
4 touches
1 conflict
0x650e90b3…213d
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 0x7c11df389c…6e2f2c
Audit this contract →
← previous block·next block →recent activity