← previous blocknext block →recent activity
Analyzing
Block #76,117,145
31 transactions · 22 stateful · 2026-05-21 20:30:36 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,117,145 · 31 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
4w05w010w111w012w013w118w019w121w222w223w324w429w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
8 touches
6 conflicts
0x41755291…977f
0x065c9d…c394
8 touches
6 conflicts
0x05eea3e3…5846
0x2a68ba…90c5
4 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
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
10 conflicts on slot 0x47b807a243…c53307
Audit this contract →
← previous block·next block →recent activity