← previous blocknext block →recent activity
Analyzing
Block #75,032,754
18 transactions · 14 stateful · 2026-05-16 19:47:11 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,032,754 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w08w29w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x765c236f…ff45
0x2a68ba…90c5
6 touches
3 conflicts
0x03f50303…02ed
0xd32edf…ff58
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9abadd09…2c50
0x065c9d…c394
3 touches
1 conflict
0x92c62273…e18e
0x065c9d…c394
3 touches
1 conflict
0xe0fb2c61…4357
0x065c9d…c394
3 touches
1 conflict
0x15cd784e…6bb0
0xa6afd3…d132
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
3 conflicts on slot 0x765c236f2d…b5ff45
Audit this contract →
← previous block·next block →recent activity