← previous blocknext block →recent activity
Analyzing
Block #87,705,812
48 transactions · 36 stateful · 2026-07-14 13:08:00 UTC
Parallelism
75/100
Blocked
64%
Avg conflicts / tx
1.88
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,705,812 · 48 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w08w115w016w117w218w319w421w522w623w724w825w926w1027w1130w231w333w134w242w244w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7a916b05…8a00
0x34b655…2a6f
8 touches
6 conflicts
0x5178c26f…e125
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x7d174519…2b01
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity