← previous blocknext block →recent activity
Analyzing
Block #87,490,422
14 transactions · 13 stateful · 2026-07-13 13:06:47 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,490,422 · 14 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
1w02w03w15w26w38w09w010w111w112w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x22f5b72a…22e0
0x34b655…2a6f
8 touches
6 conflicts
0xfbff26b1…7fb7
0x34b655…2a6f
8 touches
6 conflicts
0x7cb1d883…dc23
0x34b655…2a6f
8 touches
6 conflicts
0xaff9ebd5…245a
0x34b655…2a6f
6 touches
3 conflicts
0x5b33f5b9…4bab
0x34b655…2a6f
6 touches
3 conflicts
0x8852beb6…3929
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity