← previous blocknext block →recent activity
Analyzing
Block #87,718,220
13 transactions · 11 stateful · 2026-07-14 14:31:11 UTC
Parallelism
69/100
Blocked
55%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,718,220 · 13 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
1w02w13w25w06w17w28w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f234b05…db39
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x13510de3…1c68
0x34b655…2a6f
4 touches
1 conflict
0x190a8688…7abe
0x34b655…2a6f
4 touches
1 conflict
0x190a8688…7abf
0x34b655…2a6f
4 touches
1 conflict
0x2bfb71b5…3a04
0x34b655…2a6f
4 touches
1 conflict
0x49e0713b…0e69
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
6 conflicts on slot 0x5f234b05a2…82db39
Audit this contract →
← previous block·next block →recent activity