← previous blocknext block →recent activity
Analyzing
Block #74,216,475
11 transactions · 11 stateful · 2026-05-13 00:57:57 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.82
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,216,475 · 11 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
1w05w06w17w28w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x718f5fc1…b83c
0x065c9d…c394
4 touches
1 conflict
0xe50e8dd5…713c
0x065c9d…c394
4 touches
1 conflict
0x960fa67f…5c90
0x065c9d…c394
3 touches
1 conflict
0xf8dd55d5…07a9
0x065c9d…c394
3 touches
1 conflict
0x5fea86e9…d4df
0x065c9d…c394
3 touches
1 conflict
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