pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,125,895
← previous block
next block →
recent activity
Analyzing
Block #100,125,895
12 transactions · 11 stateful · 2026-08-29 07:34:11 UTC
Parallelism
75
/100
Blocked
18
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,125,895
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x6ad2e98b
#3
updatePrices
#4
0x5acec890
#5
0x59558d29
#6
setData
#7
0x94defb17
· blocks 2
#9
execOrders
#11
0x6a928bea
#8
0x94defb17
· blocks 1
#10
bet
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5871371c…100c
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x5871371c…1005
0x8964d7…10f8
6 touches
3 conflicts
0x5871371c…1006
0x8964d7…10f8
6 touches
3 conflicts
0x5871371c…1009
0x8964d7…10f8
6 touches
3 conflicts
0x5871371c…100a
0x8964d7…10f8
6 touches
3 conflicts
0x067806af…6081
0x8964d7…10f8
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:
0x8964d7c9…5b10f8
3 conflicts on slot
0x5871371c15…1d100c
Audit this contract →
← previous block
·
next block →
recent activity