pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,473,180
← previous block
next block →
recent activity
Analyzing
Block #99,473,180
8 transactions · 8 stateful · 2026-08-27 00:34:40 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,473,180
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
0x5acec890
· blocks 1
#4
0x928e4afa
#5
0x59558d29
#7
0x6a8f8698
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x054c8b6d…645a
0x34b655…2a6f
4 touches
1 conflict
0x51af0e92…4020
0x34b655…2a6f
4 touches
1 conflict
0x78860c4f…cade
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x171d9a84…b3b7
0x34b655…2a6f
2 touches
0 conflicts
0x24b5de61…f081
0x34b655…2a6f
2 touches
0 conflicts
0x2f358e74…1022
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
0x054c8b6def…36645a
Audit this contract →
← previous block
·
next block →
recent activity