← previous blocknext block →recent activity
Analyzing
Block #73,924,117
21 transactions · 21 stateful · 2026-05-11 16:30:21 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,924,117 · 21 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
1w02w07w08w110w112w213w114w215w116w217w318w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d652ee8…83ca
0x34b655…2a6f
6 touches
3 conflicts
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xee230b20…5a0f
0x34b655…2a6f
6 touches
3 conflicts
0x0aec204a…4ba6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2aef4269…ad47
0x34b655…2a6f
4 touches
1 conflict
0x4f483049…3cc7
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 0x9d652ee883…0e83ca
Audit this contract →
← previous block·next block →recent activity