← previous blocknext block →recent activity
Analyzing
Block #76,089,027
25 transactions · 23 stateful · 2026-05-21 17:23:17 UTC
Parallelism
24/100
Blocked
83%
Avg conflicts / tx
6.88
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #76,089,027 · 25 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w610w711w812w913w1014w1115w1216w1317w1418w1519w1620w1721w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa164d951…1534
0xe1c8b7…3022
38 touches
171 conflicts
0x12a9b76e…cb76
0x3bd359…433a
38 touches
171 conflicts
0x44ed742f…63f5
0x3bd359…433a
38 touches
171 conflicts
0x4eb758b8…b13b
0x3bd359…433a
38 touches
171 conflicts
0x67d846dd…358c
0x6661d3…7777
38 touches
171 conflicts
0x631ab234…2d48
0x9f3832…4ae4
38 touches
171 conflicts
0x631ab234…2d49
0x9f3832…4ae4
38 touches
171 conflicts
0x7cf5136f…ba69
0x9f3832…4ae4
38 touches
171 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: 0xe1c8b733…e33022
171 conflicts on slot 0xa164d95170…fa1534
Audit this contract →
← previous block·next block →recent activity