← previous blocknext block →recent activity
Analyzing
Block #74,956,263
27 transactions · 21 stateful · 2026-05-16 11:15:31 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,956,263 · 27 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
1w02w13w05w06w17w09w110w212w013w117w018w219w321w424w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e49348b…9445
0x34b655…2a6f
8 touches
6 conflicts
0x5962fd24…d5c3
0xd32edf…ff58
7 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
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
6 conflicts on slot 0x3e49348b38…839445
Audit this contract →
← previous block·next block →recent activity