← previous blocknext block →recent activity
Analyzing
Block #87,498,207
20 transactions · 18 stateful · 2026-07-13 13:58:53 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,498,207 · 20 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
1w02w13w24w06w08w111w112w213w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0xd1bb19ac…18a7
0x0a2fbf…29b1
6 touches
3 conflicts
0xd1bb19ac…18a8
0x0a2fbf…29b1
6 touches
3 conflicts
0xd1bb19ac…18ab
0x0a2fbf…29b1
6 touches
3 conflicts
0xdc296b7d…1cbb
0x0a2fbf…29b1
6 touches
3 conflicts
0xdc296b7d…1cbc
0x0a2fbf…29b1
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x63ad92a0…7912
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: 0x0a2fbf2d…f729b1
3 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity