← previous blocknext block →recent activity
Analyzing
Block #74,796,341
15 transactions · 11 stateful · 2026-05-15 17:28:04 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,796,341 · 15 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
1w05w06w17w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbb601fe7…d0d7
0x065c9d…c394
4 touches
1 conflict
0x14ede7a0…8409
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0xa7cb74…1239
4 touches
1 conflict
0x67d76404…6223
0x065c9d…c394
3 touches
1 conflict
0xc3e7031c…c98f
0x065c9d…c394
3 touches
1 conflict
0x2e2214a9…fe0d
0x5d823e…89c6
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: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity