← previous blocknext block →recent activity
Analyzing
Block #87,610,316
18 transactions · 15 stateful · 2026-07-14 02:29:28 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,610,316 · 18 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
1w04w05w18w09w211w112w313w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00562d2c…9552
0x34b655…2a6f
4 touches
1 conflict
0x11e1426c…0d03
0x34b655…2a6f
4 touches
1 conflict
0x1d826725…e975
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x4fdbc928…4a1f
0x34b655…2a6f
4 touches
1 conflict
0x4fdbc928…4a20
0x34b655…2a6f
4 touches
1 conflict
0x67c5013f…c1fc
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 0x00562d2c01…4e9552
Audit this contract →
← previous block·next block →recent activity