← previous blocknext block →recent activity
Analyzing
Block #73,987,618
14 transactions · 11 stateful · 2026-05-11 23:33:55 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,987,618 · 14 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
1w05w16w27w18w39w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xf537eaa0…73c8
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0x1a96119e…b5a2
0x065c9d…c394
3 touches
1 conflict
0xa85fd578…fcb7
0x065c9d…c394
2 touches
0 conflicts
0xaae8a649…e7aa
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity