← previous blocknext block →recent activity
Analyzing
Block #73,743,748
14 transactions · 13 stateful · 2026-05-10 20:23:43 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,743,748 · 14 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
1w02w13w28w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xc4d40bf8…7586
0xd32edf…ff58
5 touches
3 conflicts
0x0711ec2d…d973
0x34b655…2a6f
4 touches
1 conflict
0x5d70606a…1d53
0x34b655…2a6f
4 touches
1 conflict
0x5de96bd3…c60c
0x34b655…2a6f
4 touches
1 conflict
0xa009aa7b…a5ba
0x34b655…2a6f
4 touches
1 conflict
0xa80253b7…135e
0x34b655…2a6f
4 touches
1 conflict
0xd49762c9…1359
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
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity