← previous blocknext block →recent activity
Analyzing
Block #76,194,047
11 transactions · 9 stateful · 2026-05-22 05:02:41 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,194,047 · 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
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e719c7a…df63
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1cbcf514…c888
0x065c9d…c394
2 touches
0 conflicts
0x70935e43…c2a7
0x065c9d…c394
2 touches
0 conflicts
0x94f4f59f…169e
0x065c9d…c394
2 touches
0 conflicts
0xff84b819…50f6
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 0x9e719c7aca…c7df63
Audit this contract →
← previous block·next block →recent activity