← previous blocknext block →recent activity
Analyzing
Block #76,436,506
17 transactions · 14 stateful · 2026-05-23 07:57:11 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,436,506 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w27w010w311w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0000
0xf72745…ca89
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd75932c1…1e9f
0x34b655…2a6f
4 touches
1 conflict
0xf6884b1c…8b7f
0x34b655…2a6f
4 touches
1 conflict
0xfc5cb439…57c4
0x34b655…2a6f
4 touches
1 conflict
0x65ef6e8c…d10d
0xa6afd3…d132
4 touches
1 conflict
0xda693078…02d1
0xa6afd3…d132
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: 0xa6afd386…b0d132
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity