← previous blocknext block →recent activity
Analyzing
Block #76,115,365
10 transactions · 9 stateful · 2026-05-21 20:18:46 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,115,365 · 10 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
1w02w13w24w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe097de35…2766
0x065c9d…c394
6 touches
3 conflicts
0xf2f9fe89…2125
0x065c9d…c394
5 touches
3 conflicts
0x73131ffc…b46c
0x5df178…7777
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0x2c492d…444e
4 touches
1 conflict
0x00000000…0001
0x2c492d…444e
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
3 conflicts on slot 0xe097de35cb…2b2766
Audit this contract →
← previous block·next block →recent activity