← previous blocknext block →recent activity
Analyzing
Block #87,593,779
24 transactions · 24 stateful · 2026-07-14 00:38:53 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,593,779 · 24 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
2w03w15w07w011w113w116w117w218w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x17cc5ec3…ae0e
0x34b655…2a6f
4 touches
1 conflict
0x2063092b…5578
0x34b655…2a6f
4 touches
1 conflict
0x28c180e1…f1e2
0x34b655…2a6f
4 touches
1 conflict
0x29569f4d…31e2
0x34b655…2a6f
4 touches
1 conflict
0x2dda849a…d902
0x34b655…2a6f
4 touches
1 conflict
0x3259db2f…a6a0
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity