← previous blocknext block →recent activity
Analyzing
Block #87,524,951
14 transactions · 12 stateful · 2026-07-13 16:58:25 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,524,951 · 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
1w05w06w17w29w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x3a6290da…e683
0x34b655…2a6f
4 touches
1 conflict
0x5927ce81…320f
0x34b655…2a6f
4 touches
1 conflict
0x6016de75…62e0
0x34b655…2a6f
4 touches
1 conflict
0x6016de75…62e1
0x34b655…2a6f
4 touches
1 conflict
0x94cd6ce2…7b45
0x34b655…2a6f
4 touches
1 conflict
0x992fec28…420d
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity