← previous blocknext block →recent activity
Analyzing
Block #87,410,610
22 transactions · 20 stateful · 2026-07-13 04:13:11 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,410,610 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w311w412w413w014w115w016w220w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7e2f1b7…7e6f
0x34b655…2a6f
6 touches
3 conflicts
0x2b111712…0e59
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x0aa5b76b…60db
0x34b655…2a6f
6 touches
3 conflicts
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x3fc03f12…65c0
0x34b655…2a6f
4 touches
1 conflict
0x427f51fd…bd80
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
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 0xa7e2f1b7f5…cf7e6f
Audit this contract →
← previous block·next block →recent activity