pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,577,803
← previous block
next block →
recent activity
Analyzing
Block #100,577,803
14 transactions · 12 stateful · 2026-08-30 21:32:02 UTC
Parallelism
86
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,577,803
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a94a1c9
#2
0x5acec890
· blocks 2
#3
updatePrices
#5
execOrder
#6
0x59558d29
#7
execOrders
#8
execOrders
#9
aggregate3
#10
executeBatch
#11
setData
#12
execOrders
#4
0x5acec890
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd2e4fc81…163c
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x137247ba…5992
0x34b655…2a6f
2 touches
0 conflicts
0x1fb8364c…c10d
0x34b655…2a6f
2 touches
0 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
2 touches
0 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
2 touches
0 conflicts
0x5ad5e6de…e7ad
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity