← previous blocknext block →recent activity
Analyzing
Block #73,050,833
31 transactions · 26 stateful · 2026-05-07 15:22:57 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,050,833 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w17w211w219w020w121w222w023w325w129w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd984a5e4…5cfc
0x34b655…2a6f
10 touches
10 conflicts
0x2a354a63…0515
0x065c9d…c394
8 touches
6 conflicts
0x8e66da19…66b6
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0002
0x63e48b…53f2
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
10 conflicts on slot 0xd984a5e4e9…3a5cfc
Audit this contract →
← previous block·next block →recent activity