← previous blocknext block →recent activity
Analyzing
Block #76,090,288
18 transactions · 12 stateful · 2026-05-21 17:31:41 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,090,288 · 18 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
1w02w15w26w28w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50e48ab0…96fe
0x065c9d…c394
5 touches
3 conflicts
0xd30abafa…e775
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x872e51c8…ae29
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x533efb5c…354c
0x122c0d…e3fa
2 touches
0 conflicts
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
3 conflicts on slot 0x50e48ab08b…bc96fe
Audit this contract →
← previous block·next block →recent activity