← previous blocknext block →recent activity
Analyzing
Block #76,476,789
9 transactions · 9 stateful · 2026-05-23 12:25:22 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,476,789 · 9 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c913164…5c2e
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0xaa3492db…3703
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x044d556e…6564
0x065c9d…c394
2 touches
0 conflicts
0x1c500925…2579
0x065c9d…c394
2 touches
0 conflicts
0x4c4e418e…ac9c
0x065c9d…c394
2 touches
0 conflicts
0x4e248ab0…9672
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 0x1c913164f5…845c2e
Audit this contract →
← previous block·next block →recent activity