pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,237,945
← previous block
next block →
recent activity
Analyzing
Block #74,237,945
9 transactions · 9 stateful · 2026-05-13 03:20:42 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,237,945
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x39435dac
· blocks 2
#2
updateDataFeedsValuesPartial
#4
multicall
#5
setData
#6
forward
#7
0x6a03ee81
#3
0x98717539
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa26c29a3…c434
0x34b655…2a6f
6 touches
3 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x2965e2d6…5800
0x34b655…2a6f
4 touches
1 conflict
0x1fd20d14…80dd
0x34b655…2a6f
4 touches
1 conflict
0x768cffcd…2648
0x34b655…2a6f
4 touches
1 conflict
0x610af092…8ad3
0x34b655…2a6f
2 touches
0 conflicts
0xb0f1bb77…88de
0x34b655…2a6f
2 touches
0 conflicts
0xde8d683d…0d0f
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
0xa26c29a3b3…f2c434
Audit this contract →
← previous block
·
next block →
recent activity