← previous blocknext block →recent activity
Analyzing
Block #87,577,564
14 transactions · 14 stateful · 2026-07-13 22:50:26 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,577,564 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w07w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c334da6…0313
0x34b655…2a6f
4 touches
1 conflict
0x511cdf65…47ab
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0xa37c6b65…baa7
0x34b655…2a6f
4 touches
1 conflict
0xce819282…c06d
0x34b655…2a6f
4 touches
1 conflict
0xce819282…c06e
0x34b655…2a6f
4 touches
1 conflict
0xe2607c11…8fa7
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
1 conflict on slot 0x3c334da635…9b0313
Audit this contract →
← previous block·next block →recent activity