← previous blocknext block →recent activity
Analyzing
Block #75,116,911
10 transactions · 7 stateful · 2026-05-17 05:08:41 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,116,911 · 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
4w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x12c1c7e7…402d
0x065c9d…c394
2 touches
0 conflicts
0x77d2c425…0af4
0x065c9d…c394
2 touches
0 conflicts
0xabf8c969…260d
0x065c9d…c394
2 touches
0 conflicts
0xc74779b3…a56a
0x065c9d…c394
2 touches
0 conflicts
0xe65680c4…5441
0x065c9d…c394
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity