← previous blocknext block →recent activity
Analyzing
Block #87,591,624
13 transactions · 13 stateful · 2026-07-14 00:24:28 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,591,624 · 13 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
2w03w16w27w38w411w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c46e97…c1b2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x14342bd1…97aa
0x34b655…2a6f
4 touches
1 conflict
0x1750da27…5388
0x34b655…2a6f
4 touches
1 conflict
0x1de49243…4aa3
0x34b655…2a6f
4 touches
1 conflict
0x2d8a87f4…9991
0x34b655…2a6f
4 touches
1 conflict
0x47774d48…7bac
0x34b655…2a6f
4 touches
1 conflict
0x4a0be70e…91ec
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 0x99c46e97a0…cac1b2
Audit this contract →
← previous block·next block →recent activity