← previous blocknext block →recent activity
Analyzing
Block #76,211,844
9 transactions · 8 stateful · 2026-05-22 07:00:56 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,211,844 · 9 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
1w02w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fbe2f89…3174
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x083a53e3…27cc
0x065c9d…c394
3 touches
1 conflict
0x6563ce51…e8b8
0x065c9d…c394
3 touches
1 conflict
0x05f2f536…458a
0x065c9d…c394
2 touches
0 conflicts
0x317619f2…9f6b
0x065c9d…c394
2 touches
0 conflicts
0x53814631…6411
0x065c9d…c394
2 touches
0 conflicts
0x54e0ffca…dbf4
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 0x8fbe2f89db…ae3174
Audit this contract →
← previous block·next block →recent activity