← previous blocknext block →recent activity
Analyzing
Block #73,744,071
18 transactions · 16 stateful · 2026-05-10 20:25:53 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
1.28
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,744,071 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w09w110w211w312w413w517w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0xa80253b7…135e
0x34b655…2a6f
8 touches
6 conflicts
0xaa8a1c54…ead3
0x34b655…2a6f
8 touches
6 conflicts
0x8a85cf3d…2868
0x34b655…2a6f
8 touches
6 conflicts
0x908d4442…2c4b
0x34b655…2a6f
8 touches
6 conflicts
0x5d70606a…1d53
0x34b655…2a6f
8 touches
6 conflicts
0x5de96bd3…c60c
0x34b655…2a6f
8 touches
6 conflicts
0xbcb78361…78c7
0x34b655…2a6f
6 touches
3 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: Perpl
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity