pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,395,000
7 transactions · 6 stateful · 2026-05-04 14:33:52 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,395,000 · 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
1w02w14w05w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x68510731…6ac9
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xfa78d8e9…3abc
0x065c9d…c394
3 touches
1 conflict
0x28e59e33…0ce6
0x065c9d…c394
2 touches
0 conflicts
0x7592c6f5…2824
0x065c9d…c394
2 touches
0 conflicts
0xd6ae86ff…fb2c
0x065c9d…c394
2 touches
0 conflicts
0xfbc7ea4e…8690
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity