← previous blocknext block →recent activity
Analyzing
Block #76,395,717
8 transactions · 7 stateful · 2026-05-23 03:26:01 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,395,717 · 8 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
2w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2cf96c0a…538a
0x34b655…2a6f
4 touches
1 conflict
0x37d49489…9309
0x34b655…2a6f
4 touches
1 conflict
0xaa3492db…3703
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x242ff4e6…8887
0x065c9d…c394
2 touches
0 conflicts
0x62ad048c…5723
0x065c9d…c394
2 touches
0 conflicts
0x9617035a…6b3f
0x065c9d…c394
2 touches
0 conflicts
0xb1efd611…49aa
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 0x2cf96c0aa7…27538a
Audit this contract →
← previous block·next block →recent activity