← previous blocknext block →recent activity
Analyzing
Block #76,090,125
23 transactions · 22 stateful · 2026-05-21 17:30:35 UTC
Parallelism
87/100
Blocked
41%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,090,125 · 23 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
1w02w14w15w16w07w18w210w011w114w015w120w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
6 touches
3 conflicts
0xc72deae1…64c1
0xd32edf…ff58
5 touches
3 conflicts
0x12a9b76e…cb76
0x3bd359…433a
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xaa47606d…91ca
0x9f3832…4ae4
4 touches
1 conflict
0xaa47606d…91cb
0x9f3832…4ae4
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
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 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity