← previous blocknext block →recent activity
Analyzing
Block #87,342,200
14 transactions · 14 stateful · 2026-07-12 20:35:36 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,342,200 · 14 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
2w03w14w05w28w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1cda18d5…31c3
0x34b655…2a6f
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
6 touches
3 conflicts
0xfadc118d…5d64
0x34b655…2a6f
6 touches
3 conflicts
0x80ce19e2…37d3
0x34b655…2a6f
4 touches
1 conflict
0x84ecc7b6…d90e
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x9b36f19f…fa5a
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 0x1cda18d562…7031c3
Audit this contract →
← previous block·next block →recent activity