← previous blocknext block →recent activity
Analyzing
Block #77,516,010
13 transactions · 9 stateful · 2026-05-28 07:48:55 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,516,010 · 13 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
1w02w03w15w16w07w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c046a31…d8a1
0xa6afd3…d132
4 touches
1 conflict
0x40e31e14…c46c
0xa6afd3…d132
4 touches
1 conflict
0x6e4ab143…75b2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
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-WETH/USDC
1 conflict on slot 0x3c046a312a…fcd8a1
Audit this contract →
← previous block·next block →recent activity