← previous blocknext block →recent activity
Analyzing
Block #73,037,037
37 transactions · 23 stateful · 2026-05-07 13:51:02 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,037,037 · 37 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w016w017w118w219w323w025w126w229w133w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xf4730a2d…3538
0x34b655…2a6f
6 touches
3 conflicts
0x97c212c3…3985
0xd32edf…ff58
5 touches
3 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0x0b28bf77…e53a
0x34b655…2a6f
4 touches
1 conflict
0x1b9e654e…0a08
0x34b655…2a6f
4 touches
1 conflict
0x32ee90db…decc
0x34b655…2a6f
4 touches
1 conflict
0x388e001a…7e04
0x34b655…2a6f
4 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: Perpl
6 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity