← previous blocknext block →recent activity
Analyzing
Block #76,233,501
25 transactions · 17 stateful · 2026-05-22 09:25:44 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,233,501 · 25 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
2w04w15w26w37w08w19w215w016w117w021w423w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2bac2b…2cec
0x065c9d…c394
8 touches
6 conflicts
0xf3d7a307…4d63
0x065c9d…c394
8 touches
6 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
8 touches
6 conflicts
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x005fb969…2d97
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0xfe2bac2b2f…482cec
Audit this contract →
← previous block·next block →recent activity