← previous blocknext block →recent activity
Analyzing
Block #76,506,139
14 transactions · 12 stateful · 2026-05-23 15:40:49 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,506,139 · 14 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
1w02w04w15w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc6434bd…6d5c
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc906436c…b676
0xa6afd3…d132
4 touches
1 conflict
0x3424e36c…37b5
0x065c9d…c394
2 touches
0 conflicts
0x4036e360…62b1
0x065c9d…c394
2 touches
0 conflicts
0xef62bd79…65e5
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x24781048…4772
0x2a68ba…90c5
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: 0xa6afd386…b0d132
1 conflict on slot 0xcc6434bd0c…c46d5c
Audit this contract →
← previous block·next block →recent activity