← previous blocknext block →recent activity
Analyzing
Block #76,233,184
18 transactions · 13 stateful · 2026-05-22 09:23:37 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,233,184 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w510w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0xfd4bd0e6…5918
0x754704…b603
4 touches
1 conflict
0x4aa3dc54…b2b4
0xae0830…85fe
4 touches
1 conflict
0x5b7f239c…acf5
0xae0830…85fe
4 touches
1 conflict
0xc39192d6…d4df
0xae0830…85fe
4 touches
1 conflict
0x06956408…967b
0x754704…b603
4 touches
1 conflict
0x4aa3dc54…b2b1
0xae0830…85fe
4 touches
1 conflict
0x2b936aa5…05e0
0xe0b5d2…9231
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: 0xab35264b…1cfa38
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity