← previous blocknext block →recent activity
Analyzing
Block #87,294,480
13 transactions · 13 stateful · 2026-07-12 15:16:32 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,294,480 · 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
2w03w14w05w09w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4572c9a0…5cf9
0x34b655…2a6f
8 touches
6 conflicts
0x8c548107…e5b0
0x34b655…2a6f
6 touches
3 conflicts
0x2cebfc76…2320
0x34b655…2a6f
4 touches
1 conflict
0x47161afa…166c
0x34b655…2a6f
4 touches
1 conflict
0x5e68440e…097f
0x34b655…2a6f
4 touches
1 conflict
0x6538c235…62ad
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x7ae63663…9d94
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 0x4572c9a0b6…8e5cf9
Audit this contract →
← previous block·next block →recent activity