← previous blocknext block →recent activity
Analyzing
Block #75,943,850
16 transactions · 15 stateful · 2026-05-21 01:15:56 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,943,850 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w28w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x951e1996…95d1
0xa6afd3…d132
4 touches
1 conflict
0xafd59af5…5257
0xc8689a…ee79
4 touches
1 conflict
0x10f5f4d8…572e
0x34b655…2a6f
4 touches
1 conflict
0x1c03e6db…938d
0x34b655…2a6f
4 touches
1 conflict
0x74c288ff…1607
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity