← previous blocknext block →recent activity
Analyzing
Block #87,706,023
34 transactions · 32 stateful · 2026-07-14 13:09:25 UTC
Parallelism
50/100
Blocked
69%
Avg conflicts / tx
4.41
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,706,023 · 34 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
3w05w06w110w011w112w213w314w415w516w617w718w819w920w1021w1122w1223w1324w1425w1526w1627w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
34 touches
136 conflicts
0xe71ff1ef…67f8
0x0a2fbf…29b1
34 touches
136 conflicts
0xe71ff1ef…67f9
0x0a2fbf…29b1
34 touches
136 conflicts
0xe71ff1ef…67fc
0x0a2fbf…29b1
34 touches
136 conflicts
0x00000000…0005
0x370e2e…63b4
34 touches
136 conflicts
0x1bff683e…7ecb
0x754704…b603
34 touches
136 conflicts
0x55b4e430…44cb
0x754704…b603
34 touches
136 conflicts
0x8b22ec86…366e
0x0a2fbf…29b1
33 touches
136 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: 0x0a2fbf2d…f729b1
136 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity