pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,200,755
19 transactions · 11 stateful · 2026-05-08 08:00:24 UTC
Parallelism
89/100
Blocked
18%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,200,755 · 19 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
1w07w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x17cd1479…00bb
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
4 touches
1 conflict
0x3c19ea74…3051
0x065c9d…c394
2 touches
0 conflicts
0x8e66da19…66b6
0x065c9d…c394
2 touches
0 conflicts
0x93cd481c…a02a
0x065c9d…c394
2 touches
0 conflicts
0xc1bb20e9…a7a8
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity