← previous blocknext block →recent activity
Analyzing
Block #87,590,131
30 transactions · 25 stateful · 2026-07-14 00:14:29 UTC
Parallelism
57/100
Blocked
64%
Avg conflicts / tx
1.83
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,590,131 · 30 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w012w113w214w315w416w517w618w719w128w1129w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
14 touches
21 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
10 touches
10 conflicts
0x2dfde2ed…8801
0x34b655…2a6f
10 touches
10 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x201679bc…0414
0x34b655…2a6f
10 touches
10 conflicts
0x9f6c1915…6b86
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity