← previous blocknext block →recent activity
Analyzing
Block #74,951,332
9 transactions · 8 stateful · 2026-05-16 10:42:22 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,951,332 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x180edd79…1a2e
0x065c9d…c394
3 touches
1 conflict
0x4186de24…90dc
0x065c9d…c394
3 touches
1 conflict
0xb1aa8eba…ba51
0x065c9d…c394
2 touches
1 conflict
0x0659b716…8215
0x065c9d…c394
2 touches
0 conflicts
0x3c30a2fd…4afb
0x065c9d…c394
2 touches
0 conflicts
0x527ee8c7…cf75
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
1 conflict on slot 0x30276c1c08…7247b4
Audit this contract →
← previous block·next block →recent activity