pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,384,056
11 transactions · 11 stateful · 2026-05-09 04:19:45 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,384,056 · 11 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4e3b3b1…0911
0x2a68ba…90c5
4 touches
1 conflict
0xa7fe0d97…ae1c
0x2a68ba…90c5
4 touches
1 conflict
0xd8955af7…d7d5
0x065c9d…c394
4 touches
1 conflict
0x121e7300…862a
0x065c9d…c394
3 touches
1 conflict
0x719bb1e1…bd5a
0x065c9d…c394
3 touches
1 conflict
0x9baa8f36…b3f9
0x065c9d…c394
3 touches
1 conflict
0x38e4c37b…b00a
0xa6afd3…d132
3 touches
1 conflict
0xe26fc610…7e48
0x065c9d…c394
3 touches
1 conflict
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: 0x2a68ba18…8e90c5
1 conflict on slot 0xa4e3b3b1bb…130911
Audit this contract →
← previous block·next block →recent activity