← previous blocknext block →recent activity
Analyzing
Block #87,283,036
16 transactions · 14 stateful · 2026-07-12 13:59:59 UTC
Parallelism
69/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,283,036 · 16 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
2w07w18w29w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd6e61f7…3ede
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x26acd5b4…4f06
0x34b655…2a6f
4 touches
1 conflict
0x58b06598…231a
0x34b655…2a6f
4 touches
1 conflict
0x5b9e5ecc…2bc7
0x34b655…2a6f
4 touches
1 conflict
0x5c36efad…aa74
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xbd6e61f76f…523ede
Audit this contract →
← previous block·next block →recent activity