← previous blocknext block →recent activity
Analyzing
Block #76,043,834
17 transactions · 13 stateful · 2026-05-21 12:21:37 UTC
Parallelism
59/100
Blocked
54%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,043,834 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w010w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x9a3801b1…a598
0x34b655…2a6f
8 touches
6 conflicts
0xb9868b52…c77f
0x34b655…2a6f
8 touches
6 conflicts
0xce6d2591…ddeb
0x34b655…2a6f
6 touches
3 conflicts
0x3817764d…242b
0x34b655…2a6f
6 touches
3 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xdef19d99…c0a9
0x34b655…2a6f
5 touches
3 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity