pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,554,843
← previous block
next block →
recent activity
Analyzing
Block #93,554,843
10 transactions · 8 stateful · 2026-08-06 05:53:16 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,554,843
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
#2
0x928e4afa
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#5
0x3f5c179b
#7
setData
#8
withdraw
#6
0x0f6795d9
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b89ce6f…cc35
0x34b655…2a6f
4 touches
1 conflict
0x3d0a1339…f545
0x34b655…2a6f
4 touches
1 conflict
0x9132c685…1821
0x34b655…2a6f
4 touches
1 conflict
0xd192f4ed…d7ec
0x34b655…2a6f
4 touches
1 conflict
0x225c7832…e0f5
0x34b655…2a6f
2 touches
0 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x5e0b8bbe…377b
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
0x6b89ce6fa0…95cc35
Audit this contract →
← previous block
·
next block →
recent activity