pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,429,887
11 transactions · 10 stateful · 2026-05-04 18:26:20 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,429,887 · 11 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
1w04w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa22d4a11…7c5e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x21f75742…04d2
0x065c9d…c394
4 touches
2 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x09a1a0e6…3eab
0x065c9d…c394
4 touches
1 conflict
0x06897d70…caf0
0x065c9d…c394
3 touches
1 conflict
0x61f3293c…69d7
0x065c9d…c394
3 touches
1 conflict
0xcd3b36c5…584c
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 0xa22d4a118a…a67c5e
Audit this contract →
← previous block·next block →recent activity