← previous blocknext block →recent activity
Analyzing
Block #87,729,736
17 transactions · 17 stateful · 2026-07-14 15:48:13 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,729,736 · 17 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
2w03w04w16w17w212w213w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0bbc9941…4358
0x34b655…2a6f
4 touches
1 conflict
0x1a380539…8078
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x4784bb55…4ed1
0x34b655…2a6f
4 touches
1 conflict
0x53a854a3…8db8
0x34b655…2a6f
4 touches
1 conflict
0x799ee783…1f74
0x34b655…2a6f
4 touches
1 conflict
0x7e1d87b8…291c
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity