← previous blocknext block →recent activity
Analyzing
Block #76,194,097
17 transactions · 14 stateful · 2026-05-22 05:03:01 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,194,097 · 17 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
1w04w05w17w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x57dda185…e9bb
0x065c9d…c394
2 touches
0 conflicts
0x5d9889c4…bfc8
0x065c9d…c394
2 touches
0 conflicts
0x6a14a18d…6a59
0x065c9d…c394
2 touches
0 conflicts
0x6aed98d6…f068
0x065c9d…c394
2 touches
0 conflicts
0xb4bd958b…7f76
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 0xfe2bac2b2f…482cec
Audit this contract →
← previous block·next block →recent activity