← previous blocknext block →recent activity
Analyzing
Block #74,238,416
10 transactions · 10 stateful · 2026-05-13 03:23:50 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,238,416 · 10 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
3w04w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x7fe1a120…5d40
0x065c9d…c394
2 touches
0 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
2 touches
0 conflicts
0xf8a837ef…ab1f
0x065c9d…c394
2 touches
0 conflicts
0xa9988419…9f45
0x34b655…2a6f
2 touches
0 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity