← previous blocknext block →recent activity
Analyzing
Block #87,316,931
16 transactions · 15 stateful · 2026-07-12 17:46:36 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,316,931 · 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
1w02w13w04w15w26w37w49w010w511w113w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x924bac95…3f39
0x34b655…2a6f
10 touches
10 conflicts
0xcb92fdfd…a590
0x34b655…2a6f
6 touches
3 conflicts
0xf4051e95…9e4b
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x1f0f20e3…b915
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x363a4317…87d2
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 0x924bac955e…793f39
Audit this contract →
← previous block·next block →recent activity