← previous blocknext block →recent activity
Analyzing
Block #87,751,363
23 transactions · 19 stateful · 2026-07-14 18:12:54 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,751,363 · 23 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
1w03w14w26w07w111w012w115w217w319w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f46250b…3bf2
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x246c6b40…6b4e
0x065c9d…c394
5 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x59c89f2b…2f10
0x34b655…2a6f
4 touches
1 conflict
0x6016de75…62e0
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 0x6f46250b20…823bf2
Audit this contract →
← previous block·next block →recent activity