← previous blocknext block →recent activity
Analyzing
Block #76,104,526
16 transactions · 10 stateful · 2026-05-21 19:06:32 UTC
Parallelism
88/100
Blocked
10%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,104,526 · 16 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
1w04w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0d5d99e3…df71
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x23651944…03cf
0x065c9d…c394
3 touches
1 conflict
0xb7c8652f…ebce
0x1111b3…4111
2 touches
0 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e016
0x188d58…ea8e
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 0x99a2130578…57dffc
Audit this contract →
← previous block·next block →recent activity