← previous blocknext block →recent activity
Analyzing
Block #74,238,711
13 transactions · 11 stateful · 2026-05-13 03:25:48 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,238,711 · 13 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
1w03w04w17w18w29w3
- 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
6 touches
3 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0x908d4442…2c4b
0x34b655…2a6f
4 touches
1 conflict
0x5de96bd3…c60c
0x34b655…2a6f
2 touches
0 conflicts
0x8a85cf3d…2868
0x34b655…2a6f
2 touches
0 conflicts
0x9ef83c66…4437
0x34b655…2a6f
2 touches
0 conflicts
0xa974b80e…a405
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity