← previous blocknext block →recent activity
Analyzing
Block #76,577,430
10 transactions · 8 stateful · 2026-05-23 23:35:31 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,577,430 · 10 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xf1c3aac6…e559
0x1efe02…37d6
2 touches
0 conflicts
0x0782ec1b…8386
0xd42a27…01c7
2 touches
0 conflicts
0x0782ec1b…8388
0xd42a27…01c7
2 touches
0 conflicts
0xc528d4fa…236b
0xd42a27…01c7
2 touches
0 conflicts
0x1005f9aa…8bfc
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