← previous blocknext block →recent activity
Analyzing
Block #76,157,949
11 transactions · 8 stateful · 2026-05-22 01:02:27 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,157,949 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52769e03…6593
0x065c9d…c394
4 touches
1 conflict
0xefb0ec23…dffb
0x065c9d…c394
3 touches
1 conflict
0x6de57bb1…3d42
0x065c9d…c394
3 touches
1 conflict
0x12b3a3a7…a86a
0x065c9d…c394
2 touches
0 conflicts
0x497ad567…be2b
0x065c9d…c394
2 touches
0 conflicts
0x5b197885…4468
0x065c9d…c394
2 touches
0 conflicts
0x61501117…14da
0x065c9d…c394
2 touches
0 conflicts
0x8cf64ead…d164
0x065c9d…c394
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
1 conflict on slot 0x52769e0311…496593
Audit this contract →
← previous block·next block →recent activity