← previous blocknext block →recent activity
Analyzing
Block #87,588,513
15 transactions · 13 stateful · 2026-07-14 00:03:39 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,588,513 · 15 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
3w05w07w18w09w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee06e767…00d6
0x34b655…2a6f
4 touches
1 conflict
0xf0ad9713…5796
0x34b655…2a6f
4 touches
1 conflict
0xf6d317b2…05b1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xbf5467dd…2f0a
0x40c49f…2af0
4 touches
1 conflict
0x4467ecee…e95b
0x34b655…2a6f
4 touches
1 conflict
0x18904470…0ef9
0x34b655…2a6f
4 touches
1 conflict
0x7cd78950…607c
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 0xee06e76704…0e00d6
Audit this contract →
← previous block·next block →recent activity