← previous blocknext block →recent activity
Analyzing
Block #76,244,233
22 transactions · 15 stateful · 2026-05-22 10:37:07 UTC
Parallelism
91/100
Blocked
33%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,244,233 · 22 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
2w03w14w06w17w08w113w014w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9be2b99a…a959
0x34b655…2a6f
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xedb848fe…6534
0x34b655…2a6f
4 touches
1 conflict
0xe54a1f6f…18f2
0x34b655…2a6f
4 touches
1 conflict
0xa009aa7b…a5ba
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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
1 conflict on slot 0x9be2b99a82…caa959
Audit this contract →
← previous block·next block →recent activity