← previous blocknext block →recent activity
Analyzing
Block #87,410,640
21 transactions · 20 stateful · 2026-07-13 04:13:23 UTC
Parallelism
76/100
Blocked
55%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,410,640 · 21 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
1w02w13w24w05w17w28w09w113w014w115w316w117w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x095a2c84…6648
0x34b655…2a6f
10 touches
10 conflicts
0x2b5101ac…090b
0x34b655…2a6f
10 touches
10 conflicts
0x6c87ba93…686c
0x34b655…2a6f
8 touches
6 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
8 touches
6 conflicts
0x21ea036d…5d37
0x34b655…2a6f
6 touches
3 conflicts
0xc08384da…ecb7
0x34b655…2a6f
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
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: Perpl
10 conflicts on slot 0x095a2c8492…716648
Audit this contract →
← previous block·next block →recent activity