← previous blocknext block →recent activity
Analyzing
Block #76,351,010
6 transactions · 6 stateful · 2026-05-22 22:27:40 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,351,010 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0x91b81b…6d56
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1e270b63…a204
0x1efe02…37d6
2 touches
0 conflicts
0x88ddf3b9…0cee
0x91b81b…6d56
2 touches
0 conflicts
0x9560013d…8caf
0x91b81b…6d56
2 touches
0 conflicts
0x21cf1c5d…c310
0xea1b8e…c5ec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
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: LeverUp: LeverUp
1 conflict on slot 0xb6b74ae0ff…d48d5e
Audit this contract →
← previous block·next block →recent activity