← previous blocknext block →recent activity
Analyzing
Block #76,404,485
11 transactions · 7 stateful · 2026-05-23 04:24:05 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,404,485 · 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
1w02w04w05w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x1c913164…5c2e
0x34b655…2a6f
4 touches
1 conflict
0xf1b99c49…21d2
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4011fa75…7dba
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
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 0xcc4f1f1446…7caa5f
Audit this contract →
← previous block·next block →recent activity