← previous blocknext block →recent activity
Analyzing
Block #76,230,356
23 transactions · 22 stateful · 2026-05-22 09:04:41 UTC
Parallelism
78/100
Blocked
45%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,230,356 · 23 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
3w04w15w18w210w011w012w113w014w116w017w119w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x388e001a…7e04
0x34b655…2a6f
8 touches
6 conflicts
0xf853eb8e…4027
0x34b655…2a6f
6 touches
3 conflicts
0x68728b15…33fc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0x2c492d…444e
4 touches
1 conflict
0x00000000…0001
0x2c492d…444e
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xdd70bea3…1ffe
0x3bd359…433a
4 touches
1 conflict
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity