← previous blocknext block →recent activity
Analyzing
Block #73,216,491
17 transactions · 17 stateful · 2026-05-08 09:45:00 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
1.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,216,491 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w08w09w110w211w112w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x0b390c61…dc07
0x065c9d…c394
8 touches
6 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x0b68c03a…009a
0x065c9d…c394
2 touches
0 conflicts
0x78223073…9268
0x065c9d…c394
2 touches
0 conflicts
0x9679c6db…f787
0x065c9d…c394
2 touches
0 conflicts
0xb5ae217a…4aab
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
15 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity