← previous blocknext block →recent activity
Analyzing
Block #87,622,462
14 transactions · 11 stateful · 2026-07-14 03:50:40 UTC
Parallelism
86/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,622,462 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe63cb2d0…c66f
0x34b655…2a6f
4 touches
1 conflict
0x7138c945…f6a8
0x34b655…2a6f
4 touches
1 conflict
0x78cbb28a…27c3
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x91320c47…c941
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x99080043…b90f
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 0xe63cb2d004…37c66f
Audit this contract →
← previous block·next block →recent activity