pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,818,753
← previous block
next block →
recent activity
Analyzing
Block #99,818,753
12 transactions · 12 stateful · 2026-08-28 05:46:17 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,818,753
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x6ad2e98b
#3
execOrders
#4
0x5acec890
#5
0x5acec890
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x3f5c179b
#10
0x94defb17
· blocks 1
#11
bet
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0xd293b804…1bbc
0x8964d7…10f8
4 touches
1 conflict
0xd293b804…1bbd
0x8964d7…10f8
4 touches
1 conflict
0xd293b804…1bc0
0x8964d7…10f8
4 touches
1 conflict
0xd293b804…1bc1
0x8964d7…10f8
4 touches
1 conflict
0xd293b804…1bc3
0x8964d7…10f8
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0xf7640726…19a2
0x2a68ba…90c5
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:
0x8964d7c9…5b10f8
1 conflict on slot
0x0000000000…000008
Audit this contract →
← previous block
·
next block →
recent activity