← previous blocknext block →recent activity
Analyzing
Block #76,088,640
30 transactions · 20 stateful · 2026-05-21 17:20:42 UTC
Parallelism
87/100
Blocked
45%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,088,640 · 30 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
1w03w04w15w26w08w111w217w018w119w222w223w026w328w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
6 touches
3 conflicts
0x5d70606a…1d53
0x34b655…2a6f
6 touches
3 conflicts
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0x68728b15…33fc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x0b28bf77…e53a
0x34b655…2a6f
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
3 conflicts on slot 0x388e001a16…e57e04
Audit this contract →
← previous block·next block →recent activity