← previous blocknext block →recent activity
Analyzing
Block #76,090,731
40 transactions · 25 stateful · 2026-05-21 17:34:39 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,090,731 · 40 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w39w210w419w020w121w222w323w436w037w138w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5180f24b…0b96
0xd10cf1…7777
10 touches
10 conflicts
0x00000000…0001
0xd57e82…8ed4
10 touches
10 conflicts
0x00000000…0000
0xd57e82…8ed4
10 touches
10 conflicts
0x6ac11407…0bcc
0x3bd359…433a
10 touches
10 conflicts
0xa472d565…9fe4
0x3bd359…433a
10 touches
10 conflicts
0x44ad89ba…cf83
0xd10cf1…7777
10 touches
10 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0002
0x63e48b…53f2
6 touches
3 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: 0xd10cf120…657777
10 conflicts on slot 0x5180f24b2a…b80b96
Audit this contract →
← previous block·next block →recent activity