← previous blocknext block →recent activity
Analyzing
Block #75,839,473
27 transactions · 21 stateful · 2026-05-20 13:39:58 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,839,473 · 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
2w04w05w16w27w38w49w010w111w220w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0beded98…0387
0x2b7827…e63c
10 touches
10 conflicts
0x00000000…0000
0xdda159…83e7
10 touches
10 conflicts
0x00000000…0004
0xdda159…83e7
10 touches
10 conflicts
0x7f748e57…d6eb
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0002
0xdda159…83e7
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x3c83275e…d7c2
0x34b655…2a6f
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
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: 0x2b7827b6…ebe63c
10 conflicts on slot 0x0beded984a…f90387
Audit this contract →
← previous block·next block →recent activity