← previous blocknext block →recent activity
Analyzing
Block #87,787,645
20 transactions · 19 stateful · 2026-07-14 22:15:36 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,787,645 · 20 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
2w03w14w05w16w27w38w414w015w116w218w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x9ae859db…2d84
0x34b655…2a6f
6 touches
3 conflicts
0xb59b0c85…f36c
0x34b655…2a6f
6 touches
3 conflicts
0xbd6e61f7…3ede
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x2549dda6…9e24
0x34b655…2a6f
6 touches
3 conflicts
0x28c62bca…b746
0x34b655…2a6f
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity