← previous blocknext block →recent activity
Analyzing
Block #87,349,060
28 transactions · 26 stateful · 2026-07-12 21:21:27 UTC
Parallelism
39/100
Blocked
73%
Avg conflicts / tx
4.04
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,349,060 · 28 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w714w615w716w820w922w1125w1426w1527w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x4572c9a0…5cf9
0x34b655…2a6f
18 touches
36 conflicts
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x326a02b5…8dad
0x34b655…2a6f
16 touches
28 conflicts
0xdbc62196…3245
0x34b655…2a6f
12 touches
15 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
12 touches
15 conflicts
0xc2dda872…7e3e
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity