← previous blocknext block →recent activity
Analyzing
Block #87,490,195
21 transactions · 20 stateful · 2026-07-13 13:05:16 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.95
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,490,195 · 21 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
1w02w13w24w05w17w08w29w310w011w113w214w315w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cb1d883…dc23
0x34b655…2a6f
8 touches
6 conflicts
0x3cb4b659…f735
0x34b655…2a6f
8 touches
6 conflicts
0x5b33f5b9…4bab
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
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 0x7cb1d883b4…e0dc23
Audit this contract →
← previous block·next block →recent activity