← previous blocknext block →recent activity
Analyzing
Block #87,045,516
12 transactions · 12 stateful · 2026-07-11 11:31:51 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,045,516 · 12 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
2w03w16w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d43cc69…6f83
0x34b655…2a6f
6 touches
3 conflicts
0xfcdb5918…2b49
0x34b655…2a6f
4 touches
1 conflict
0x4af2cce5…16c4
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1aa
0xb1dbf0…c0d3
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x0d43cc69f6…c46f83
Audit this contract →
← previous block·next block →recent activity