← previous blocknext block →recent activity
Analyzing
Block #87,496,990
16 transactions · 14 stateful · 2026-07-13 13:50:44 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,496,990 · 16 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
2w04w07w08w19w211w112w315w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd655b8…bf89
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x466a76c3…7a61
0x851145…3f07
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xfa4abfe1…582c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x16916afe…e61b
0x851145…3f07
4 touches
1 conflict
0x0733be30…112f
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
6 conflicts on slot 0xfdd655b80c…53bf89
Audit this contract →
← previous block·next block →recent activity