← previous blocknext block →recent activity
Analyzing
Block #73,216,529
12 transactions · 11 stateful · 2026-05-08 09:45:15 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,216,529 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0b4effdb…bbc1
0x065c9d…c394
2 touches
0 conflicts
0x0b68c03a…009a
0x065c9d…c394
2 touches
0 conflicts
0x78223073…9268
0x065c9d…c394
2 touches
0 conflicts
0x9b10ee0b…6658
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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity