pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,114,924
← previous block
next block →
recent activity
Analyzing
Block #96,114,924
20 transactions · 20 stateful · 2026-08-15 05:02:47 UTC
Parallelism
40
/100
Blocked
60
%
Avg conflicts / tx
3.35
Longest chain
12
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,114,924
· 20 txs across 12 waves · depth 12
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
wave
w10
wave
w11
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#3
0x5acec890
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
setData
#7
execFwdPositionOpsV2
#8
0xb2d4797b
· blocks 11
#2
0xab083028
#9
0xb2d4797b
· blocks 10
#10
0xb2d4797b
· blocks 9
#11
0xb2d4797b
· blocks 8
#12
0xb2d4797b
· blocks 7
#13
0xb2d4797b
· blocks 6
#14
0xb2d4797b
· blocks 5
#15
0xb2d4797b
· blocks 4
#16
0xb2d4797b
· blocks 3
#17
0xb2d4797b
· blocks 2
#18
0xb2d4797b
· blocks 1
#19
0xb2d4797b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w0
9
w1
10
w2
11
w3
12
w4
13
w5
14
w6
15
w7
16
w8
17
w9
18
w10
19
w11
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
24 touches
66 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08d53462…97ef
0x2b46c0…1669
2 touches
0 conflicts
0x5a409e7f…09b6
0x2b46c0…1669
2 touches
0 conflicts
0x7a12283f…b18a
0x2b46c0…1669
2 touches
0 conflicts
0x8b2c44b4…7e59
0x2b46c0…1669
2 touches
0 conflicts
0x915c095e…c1e5
0x2b46c0…1669
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:
0x59df8637…6d2780
66 conflicts on slot
0x0000000000…000031
Audit this contract →
← previous block
·
next block →
recent activity