← previous blocknext block →recent activity
Analyzing
Block #87,738,364
33 transactions · 32 stateful · 2026-07-14 16:45:56 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
1.52
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,738,364 · 33 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
1w02w13w26w07w19w010w111w212w213w314w415w516w621w823w224w926w128w331w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
8 touches
6 conflicts
0x6c2aa5be…d808
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd274e3f6…f155
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity