← previous blocknext block →recent activity
Analyzing
Block #87,616,456
16 transactions · 13 stateful · 2026-07-14 03:10:32 UTC
Parallelism
56/100
Blocked
62%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,616,456 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w18w29w310w411w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfece6a0e…3030
0x34b655…2a6f
10 touches
10 conflicts
0x745952b2…d90c
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7c9a221a…782b
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x39d45d52…8fa9
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 0xfece6a0e7d…ca3030
Audit this contract →
← previous block·next block →recent activity