← previous blocknext block →recent activity
Analyzing
Block #75,619,118
13 transactions · 8 stateful · 2026-05-19 13:11:35 UTC
Parallelism
85/100
Blocked
13%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,619,118 · 13 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
1w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4818a80e…00d2
0x065c9d…c394
2 touches
0 conflicts
0x582a3a62…76cb
0x065c9d…c394
2 touches
0 conflicts
0x97dc9fd8…85df
0x065c9d…c394
2 touches
0 conflicts
0x9c761850…8af2
0x065c9d…c394
2 touches
0 conflicts
0xa786dfc3…5b61
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
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: Kuru Exchange: MarginAccount
1 conflict on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity