← previous blocknext block →recent activity
Analyzing
Block #87,504,814
26 transactions · 20 stateful · 2026-07-13 14:43:08 UTC
Parallelism
81/100
Blocked
30%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,504,814 · 26 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
4w05w17w08w115w116w018w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x4dc6cd61…f674
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x29856edf…841b
0x34b655…2a6f
4 touches
1 conflict
0x2c5b1ed3…b124
0x34b655…2a6f
4 touches
1 conflict
0x3531ea1c…d294
0x34b655…2a6f
4 touches
1 conflict
0x3cb4b659…f735
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 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity