pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,758,677
← previous block
next block →
recent activity
Analyzing
Block #89,758,677
6 transactions · 5 stateful · 2026-07-23 23:10:30 UTC
Parallelism
67
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,758,677
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#3
0x0f6795d9
#4
0x6a629fdd
#5
setData
#2
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b96d534…b6b5
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2ac796c1…5bbc
0x34b655…2a6f
2 touches
0 conflicts
0x446e4f62…f7b6
0x34b655…2a6f
2 touches
0 conflicts
0x53142478…5458
0x34b655…2a6f
2 touches
0 conflicts
0x6b47245e…a342
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0x2b96d534a5…d0b6b5
Audit this contract →
← previous block
·
next block →
recent activity