pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,453,579
← previous block
next block →
recent activity
Analyzing
Block #100,453,579
15 transactions · 12 stateful · 2026-08-30 11:07:06 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,453,579
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
#3
matchOrders
#4
updatePrices
#5
0x6ad2e98b
#6
0xab083028
#7
0x59558d29
· blocks 1
#9
0xfa8e82…0964
#10
setData
#11
handleOps
#12
execFwdPositionOpsV2
#13
updateTemporalNumericValuesV1
#14
transfer
#8
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0371bfdd…0750
0x34b655…2a6f
2 touches
0 conflicts
0xc621b20b…89de
0x5ff137…2789
2 touches
0 conflicts
0x06b5e8e3…6e2a
0x754704…b603
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity