← previous blocknext block →recent activity
Analyzing
Block #87,579,163
23 transactions · 19 stateful · 2026-07-13 23:01:08 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,579,163 · 23 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
2w03w14w05w26w37w08w412w513w619w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x925c118c…a1d8
0x34b655…2a6f
8 touches
6 conflicts
0x07f69062…03ec
0x34b655…2a6f
8 touches
6 conflicts
0xd026fe03…7748
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdb7c435f…f490
0x34b655…2a6f
6 touches
3 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0xe2b73778…9fac
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 0x925c118c7b…bea1d8
Audit this contract →
← previous block·next block →recent activity