← previous blocknext block →recent activity
Analyzing
Block #75,989,775
15 transactions · 15 stateful · 2026-05-21 06:21:48 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,989,775 · 15 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
1w02w04w05w16w07w08w19w111w112w213w314w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f9f01…a8ac
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x255021f1…43d9
0x5afd3e…7620
4 touches
1 conflict
0x7226618d…5934
0x065c9d…c394
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb82
0x1b6862…e19c
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
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
6 conflicts on slot 0x676f9f01ee…dea8ac
Audit this contract →
← previous block·next block →recent activity