← previous blocknext block →recent activity
Analyzing
Block #87,410,434
25 transactions · 22 stateful · 2026-07-13 04:12:00 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,410,434 · 25 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
1w02w13w04w15w28w09w110w312w413w014w115w016w218w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc79e6364…f887
0x34b655…2a6f
6 touches
3 conflicts
0xd1e54517…96c8
0x34b655…2a6f
6 touches
3 conflicts
0xfc371f5e…0955
0x34b655…2a6f
6 touches
3 conflicts
0x4f17dc85…c493
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x3ce1717e…c639
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity