← previous blocknext block →recent activity
Analyzing
Block #76,140,442
11 transactions · 9 stateful · 2026-05-21 23:05:43 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,140,442 · 11 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
1w04w15w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x7e731ca6…e5b2
0x065c9d…c394
2 touches
0 conflicts
0x8f313589…99bf
0x065c9d…c394
2 touches
0 conflicts
0xe32a7616…5f38
0x065c9d…c394
2 touches
0 conflicts
0xe9af6b1d…61eb
0x065c9d…c394
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: Perpl
1 conflict on slot 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity