← previous blocknext block →recent activity
Analyzing
Block #87,525,082
17 transactions · 14 stateful · 2026-07-13 16:59:19 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,525,082 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w210w311w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a6290da…e683
0x34b655…2a6f
8 touches
6 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
6 touches
3 conflicts
0x6f7baf78…77a9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
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 0x3a6290da4d…93e683
Audit this contract →
← previous block·next block →recent activity