← previous blocknext block →recent activity
Analyzing
Block #74,238,429
10 transactions · 7 stateful · 2026-05-13 03:23:55 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,238,429 · 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
1w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf8a837ef…ab1f
0x065c9d…c394
4 touches
1 conflict
0xcf9011e6…82a6
0x065c9d…c394
3 touches
1 conflict
0xc4c83566…df31
0x065c9d…c394
3 touches
1 conflict
0xa4315cbe…f7dd
0x065c9d…c394
2 touches
0 conflicts
0xf2251bfc…2923
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