← previous blocknext block →recent activity
Analyzing
Block #87,611,457
23 transactions · 19 stateful · 2026-07-14 02:37:06 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,611,457 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w213w314w015w416w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa435dee8…f2be
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x59ef452c…8284
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x7bb9a5e6…dbb6
0x34b655…2a6f
4 touches
1 conflict
0x8b789f68…8ace
0x34b655…2a6f
4 touches
1 conflict
0x9e5e32a2…77e1
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 0xa435dee840…eef2be
Audit this contract →
← previous block·next block →recent activity