← previous blocknext block →recent activity
Analyzing
Block #75,016,817
25 transactions · 19 stateful · 2026-05-16 18:01:05 UTC
Parallelism
84/100
Blocked
53%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,016,817 · 25 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
1w02w13w24w38w110w013w014w015w116w217w318w122w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d394876…c488
0x402807…5159
8 touches
6 conflicts
0x21c137b8…3a77
0x3bd359…433a
8 touches
6 conflicts
0xb34209a2…164d
0x402807…5159
8 touches
6 conflicts
0x00000000…0008
0x509771…3c7b
8 touches
6 conflicts
0x0d66cecf…9214
0xd32edf…ff58
7 touches
6 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
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: OCTOMON (OCTOMON)
6 conflicts on slot 0x4d3948760c…2ac488
Audit this contract →
← previous block·next block →recent activity