pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,501,070
8 transactions · 6 stateful · 2026-05-05 02:20:22 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,501,070 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7354cf3a…f270
0x065c9d…c394
4 touches
1 conflict
0xcc2c253d…b51e
0x065c9d…c394
4 touches
1 conflict
0xf90e9a90…75c7
0x065c9d…c394
3 touches
1 conflict
0xc45ca38c…357a
0x065c9d…c394
3 touches
1 conflict
0x6f5fa1e4…3849
0x065c9d…c394
3 touches
1 conflict
0x3d4351bb…3add
0x065c9d…c394
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity