← previous blocknext block →recent activity
Analyzing
Block #87,586,431
16 transactions · 15 stateful · 2026-07-13 23:49:44 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,586,431 · 16 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
1w06w17w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3688185…9b36
0x34b655…2a6f
8 touches
6 conflicts
0x0fedf54f…57fc
0x34b655…2a6f
4 touches
1 conflict
0x13938a09…5f88
0x34b655…2a6f
4 touches
1 conflict
0x14fe1598…d0ba
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x2a0a4580…9128
0x34b655…2a6f
4 touches
1 conflict
0x3a3b4014…73c3
0x34b655…2a6f
4 touches
1 conflict
0x3a6290da…e683
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 0xc36881859a…c49b36
Audit this contract →
← previous block·next block →recent activity