pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,891,679
← previous block
next block →
recent activity
Analyzing
Block #100,891,679
11 transactions · 10 stateful · 2026-08-31 23:51:20 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,891,679
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xa96df62f
#4
0x59558d29
#5
setData
#6
execFwdPositionOpsV2
#7
handleOps
· blocks 1
#9
placeAndExecuteMarketSell
#10
0x6a9613f0
#2
0x0c7abd22
#8
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82160e43…025d
0xd5d960…eaee
4 touches
1 conflict
0x1a4179d3…0f26
0x068f22…7908
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x35801c67…bcc2
0x1b6862…e19c
4 touches
1 conflict
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:
0xd5d960e8…a1eaee
1 conflict on slot
0x82160e439e…88025d
Audit this contract →
← previous block
·
next block →
recent activity