← previous blocknext block →recent activity
Analyzing
Block #76,233,520
12 transactions · 11 stateful · 2026-05-22 09:25:52 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,233,520 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w16w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0xdf869ad5…25df
0x065c9d…c394
4 touches
1 conflict
0x9fc6ea79…e2dc
0x34b655…2a6f
4 touches
1 conflict
0xce7ad882…f478
0x065c9d…c394
3 touches
1 conflict
0x7d7d7772…d210
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity