pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,644,409
← previous block
next block →
recent activity
Analyzing
Block #90,644,409
8 transactions · 8 stateful · 2026-07-27 01:48:02 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,644,409
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a66b94a
#2
0x0f6795d9
· blocks 2
#3
0x3f5c179b
#5
0x39435dac
#6
setData
#4
0x0f6795d9
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cab9ea4…924f
0x34b655…2a6f
4 touches
1 conflict
0x24eaf46d…8c2e
0x34b655…2a6f
4 touches
1 conflict
0x26d1c221…4d2a
0x34b655…2a6f
4 touches
1 conflict
0x94ddea60…a24d
0x34b655…2a6f
4 touches
1 conflict
0x94e68337…5eb0
0x34b655…2a6f
4 touches
1 conflict
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
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
0x0cab9ea4ff…32924f
Audit this contract →
← previous block
·
next block →
recent activity