← previous blocknext block →recent activity
Analyzing
Block #76,090,918
28 transactions · 20 stateful · 2026-05-21 17:35:52 UTC
Parallelism
86/100
Blocked
50%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,090,918 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w011w012w113w314w015w116w217w324w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5180f24b…0b96
0xd10cf1…7777
8 touches
6 conflicts
0x00000000…0000
0xd57e82…8ed4
8 touches
6 conflicts
0x44ad89ba…cf83
0xd10cf1…7777
8 touches
6 conflicts
0x00000000…0001
0xd57e82…8ed4
8 touches
6 conflicts
0x6ac11407…0bcc
0x3bd359…433a
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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
6 conflicts on slot 0x5180f24b2a…b80b96
Audit this contract →
← previous block·next block →recent activity