← previous blocknext block →recent activity
Analyzing
Block #73,964,541
10 transactions · 9 stateful · 2026-05-11 20:59:11 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,964,541 · 10 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
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0655ca7e…2676
0x065c9d…c394
2 touches
0 conflicts
0x419eedf0…a9b3
0x065c9d…c394
2 touches
0 conflicts
0x5c5229c5…0ce5
0x065c9d…c394
2 touches
0 conflicts
0x85fda8e5…bf7c
0x065c9d…c394
2 touches
0 conflicts
0xd1ee1cfc…ac91
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity