← previous blocknext block →recent activity
Analyzing
Block #87,616,546
17 transactions · 12 stateful · 2026-07-14 03:11:08 UTC
Parallelism
53/100
Blocked
58%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,616,546 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w210w311w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0376dd2e…48ad
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x4e970d38…d1c4
0x34b655…2a6f
8 touches
6 conflicts
0x745952b2…d90c
0x34b655…2a6f
8 touches
6 conflicts
0x8252706a…7ca5
0x34b655…2a6f
8 touches
6 conflicts
0xbc4e7b49…3d2d
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
6 conflicts on slot 0x0376dd2eda…1648ad
Audit this contract →
← previous block·next block →recent activity