pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,999,736
← previous block
next block →
recent activity
Analyzing
Block #91,999,736
12 transactions · 10 stateful · 2026-07-31 19:29:36 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,999,736
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0x0f6795d9
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
0x39435dac
#7
0x39435dac
#8
setData
#9
0x0f6795d9
#10
0x39435dac
#11
0x59558d29
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e0c66fe…796f
0x1e2721…7805
4 touches
1 conflict
0x431fa96d…6ac0
0x754704…b603
4 touches
1 conflict
0x70a53d84…2d91
0x754704…b603
4 touches
1 conflict
0xe128028b…5633
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0x1e2721…7805
4 touches
1 conflict
0x7aa512ae…d2e0
0x754704…b603
2 touches
0 conflicts
0x7e8cd4a2…8fc0
0x754704…b603
2 touches
0 conflicts
0x7f03e539…f4cc
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:
0x1e27219e…bf7805
1 conflict on slot
0x0e0c66fe54…87796f
Audit this contract →
← previous block
·
next block →
recent activity