← previous blocknext block →recent activity
Analyzing
Block #74,901,511
13 transactions · 11 stateful · 2026-05-16 05:09:27 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,901,511 · 13 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
1w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0xeb246f52…0af8
0x065c9d…c394
3 touches
1 conflict
0xa787b204…ab8a
0x065c9d…c394
3 touches
1 conflict
0xd44f4587…8179
0x065c9d…c394
3 touches
1 conflict
0x0439069a…9c97
0x065c9d…c394
3 touches
1 conflict
0x95d07e8e…16d9
0x065c9d…c394
2 touches
0 conflicts
0xeaa2d314…e82a
0x065c9d…c394
2 touches
0 conflicts
0xec4edb61…6f07
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: Market-MON/USDC
1 conflict on slot 0xf3d7a307cc…f14d63
Audit this contract →
← previous block·next block →recent activity