pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,458,017
← previous block
next block →
recent activity
Analyzing
Block #92,458,017
7 transactions · 5 stateful · 2026-08-02 09:54:22 UTC
Parallelism
57
/100
Blocked
40
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,458,017
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x4d8dc985
· blocks 2
#3
0x0f6795d9
#5
0x6a6f1446
#6
setData
#2
0x0f6795d9
· blocks 1
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb2b68a7…8cba
0x34b655…2a6f
6 touches
3 conflicts
0x6f900be0…cd6e
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x17f5dec8…3332
0x34b655…2a6f
2 touches
0 conflicts
0x1b0ced27…6b87
0x34b655…2a6f
2 touches
0 conflicts
0x39088193…6d6b
0x34b655…2a6f
2 touches
0 conflicts
0x427d1120…4eb1
0x34b655…2a6f
2 touches
0 conflicts
0x43e15ca4…039d
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
3 conflicts on slot
0xcb2b68a714…ba8cba
Audit this contract →
← previous block
·
next block →
recent activity