← previous blocknext block →recent activity
Analyzing
Block #87,671,308
23 transactions · 20 stateful · 2026-07-14 09:17:07 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,671,308 · 23 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
1w02w03w15w06w17w28w315w416w117w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x99ee776a…053a
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x487aa334…7ef2
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7fe97198…79ab
0x34b655…2a6f
8 touches
6 conflicts
0x8b46e9d1…e148
0x34b655…2a6f
8 touches
6 conflicts
0xfa213e57…62b4
0x34b655…2a6f
8 touches
6 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: Perpl
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity