← previous blocknext block →recent activity
Analyzing
Block #87,351,082
13 transactions · 13 stateful · 2026-07-12 21:34:58 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,351,082 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w17w29w010w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6016de75…62e0
0x34b655…2a6f
4 touches
1 conflict
0x6016de75…62e1
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x824dc081…e4f1
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa55c4598…2988
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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 0x6016de752c…f462e0
Audit this contract →
← previous block·next block →recent activity