← previous blocknext block →recent activity
Analyzing
Block #75,918,984
15 transactions · 10 stateful · 2026-05-20 22:30:25 UTC
Parallelism
87/100
Blocked
20%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,918,984 · 15 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
5w06w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc079cc93…b57b
0xea1b8e…c5ec
4 touches
1 conflict
0x0a809ce1…7894
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00bac013…a28c
0x91b81b…6d56
4 touches
1 conflict
0x25b00bf5…3e2e
0xea1b8e…c5ec
4 touches
1 conflict
0x9d9f3717…44e7
0x34b655…2a6f
3 touches
1 conflict
0x76e96198…eec4
0x2a68ba…90c5
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 0xc079cc93c0…eeb57b
Audit this contract →
← previous block·next block →recent activity