← previous blocknext block →recent activity
Analyzing
Block #76,213,514
14 transactions · 11 stateful · 2026-05-22 07:12:10 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,213,514 · 14 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
1w02w16w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0xbf37bdd8…8751
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x8221fa2d…f67f
0x065c9d…c394
2 touches
0 conflicts
0xa0169597…6e62
0x065c9d…c394
2 touches
0 conflicts
0xbca5aa88…7d30
0x065c9d…c394
2 touches
0 conflicts
0xf0c81f8b…eb1f
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity