pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,438,748
← previous block
next block →
recent activity
Analyzing
Block #93,438,748
13 transactions · 11 stateful · 2026-08-05 20:09:39 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,438,748
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xeb282f7f
#3
0x5acec890
· blocks 1
#4
0x5acec890
#6
0x5acec890
#7
permit2TransferAndMulticall
#8
updateDataFeedsValuesPartial
#9
0x0f6795d9
#10
0x0f6795d9
#11
setData
#12
0xc7e3ec2c
#5
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x1e2721…7805
2 touches
0 conflicts
0x0e0c66fe…796f
0x1e2721…7805
2 touches
0 conflicts
0x630465cf…7205
0x1efe02…37d6
2 touches
0 conflicts
0x0e854949…baa7
0x754704…b603
2 touches
0 conflicts
0x29ba534c…fe06
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:
Perpl
1 conflict on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity