← previous blocknext block →recent activity
Analyzing
Block #75,427,007
10 transactions · 6 stateful · 2026-05-18 15:42:12 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,427,007 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x4ebc22e7…0702
0x34b655…2a6f
4 touches
1 conflict
0x60b2fe0b…dc32
0x34b655…2a6f
4 touches
1 conflict
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0xe48d3f8d…fc68
0xd32edf…ff58
3 touches
1 conflict
0x512bbf59…a2c4
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x6ae8eec9…d97e
0x065c9d…c394
2 touches
0 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
1 conflict on slot 0x085df2c147…d2305a
Audit this contract →
← previous block·next block →recent activity