pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,877,443
← previous block
next block →
recent activity
Analyzing
Block #100,877,443
12 transactions · 10 stateful · 2026-08-31 22:39:44 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,877,443
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#3
0x5acec890
#4
0x5acec890
#5
0x59558d29
#6
execPerpOps
#7
execPerpOps
#8
execFwdPositionOpsV2
#9
0xed82b078
#11
setData
#2
0xab083028
· blocks 1
#10
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5b089a0…e222
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4213f1c0…219a
0x2a68ba…90c5
2 touches
0 conflicts
0x08d53462…97ef
0x34ae4d…3fc5
2 touches
0 conflicts
0x5a409e7f…09b6
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…1867
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…1868
0x34ae4d…3fc5
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xd5b089a03d…f8e222
Audit this contract →
← previous block
·
next block →
recent activity