← previous blocknext block →recent activity
Analyzing
Block #74,666,285
17 transactions · 10 stateful · 2026-05-15 02:59:31 UTC
Parallelism
88/100
Blocked
40%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,666,285 · 17 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
4w06w08w09w112w113w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x3f67787a…cc3c
0xd32edf…ff58
3 touches
1 conflict
0xce206118…c93d
0x065c9d…c394
3 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5d
0x188d58…ea8e
2 touches
0 conflicts
0x7c403af1…31b1
0x3bd359…433a
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