← previous blocknext block →recent activity
Analyzing
Block #87,640,066
14 transactions · 13 stateful · 2026-07-14 05:48:25 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,640,066 · 14 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
1w02w13w06w17w28w39w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe4e62b8…9ade
0x34b655…2a6f
4 touches
1 conflict
0xf3e18c38…f1b9
0x34b655…2a6f
4 touches
1 conflict
0xfcad4d96…c690
0x34b655…2a6f
4 touches
1 conflict
0xfcad4d96…c691
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x124c94b1…9a5d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xfe4e62b849…5b9ade
Audit this contract →
← previous block·next block →recent activity