pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,974,470
← previous block
next block →
recent activity
Analyzing
Block #72,974,470
8 transactions · 8 stateful · 2026-05-07 06:54:34 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
#72,974,470
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xeffdedb0
#5
setData
#6
0x39435dac
· blocks 1
#2
0x0c7abd22
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe783dfa4…5499
0x1b6862…e19c
4 touches
1 conflict
0xc79c823f…0b7f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdaca243a…f9de
0x34b655…2a6f
4 touches
1 conflict
0xf4730a2d…3538
0x34b655…2a6f
4 touches
1 conflict
0x001b451a…0ce1
0x065c9d…c394
4 touches
1 conflict
0x2b1dbec6…19b1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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:
0x1b68626d…2de19c
1 conflict on slot
0xe783dfa4d2…185499
Audit this contract →
← previous block
·
next block →
recent activity