← previous blocknext block →recent activity
Analyzing
Block #87,524,688
18 transactions · 13 stateful · 2026-07-13 16:56:38 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,524,688 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w211w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x17cc5ec3…ae0e
0x34b655…2a6f
6 touches
3 conflicts
0x0ae85bb4…7370
0x34b655…2a6f
4 touches
1 conflict
0x0fa6e69d…16cb
0x34b655…2a6f
4 touches
1 conflict
0x1ae78ca0…5cca
0x34b655…2a6f
4 touches
1 conflict
0x4e10224d…58d3
0x34b655…2a6f
4 touches
1 conflict
0x4fbb4fea…e31b
0x34b655…2a6f
4 touches
1 conflict
0x6b2ba712…0214
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity