← previous blocknext block →recent activity
Analyzing
Block #76,036,691
12 transactions · 12 stateful · 2026-05-21 11:34:06 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,036,691 · 12 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
1w02w03w14w05w16w18w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0x65815f85…3dfa
0xd32edf…ff58
5 touches
3 conflicts
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xa0dd011c…ef25
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xab31345a…7a99
0x065c9d…c394
3 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 0x443a3e479f…3af4a4
Audit this contract →
← previous block·next block →recent activity