pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,314,889
7 transactions · 6 stateful · 2026-05-04 05:40:08 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,314,889 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bbbf80a…7fd1
0x065c9d…c394
6 touches
3 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb81
0x1b6862…e19c
4 touches
1 conflict
0x3f9845a9…de61
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0003
0x059114…ac3b
2 touches
0 conflicts
0x60d1d229…58cb
0x059114…ac3b
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: 0x065c9d28…a9c394
3 conflicts on slot 0x3bbbf80aaf…507fd1
Audit this contract →
← previous block·next block →recent activity