← previous blocknext block →recent activity
Analyzing
Block #87,513,523
18 transactions · 18 stateful · 2026-07-13 15:41:25 UTC
Parallelism
61/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,513,523 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w311w412w315w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x201c5590…31fb
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x36adf095…e10f
0x34b655…2a6f
4 touches
1 conflict
0x46870010…0b51
0x34b655…2a6f
4 touches
1 conflict
0x554115ac…e699
0x34b655…2a6f
4 touches
1 conflict
0x5e17e5be…d212
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 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity