← previous blocknext block →recent activity
Analyzing
Block #74,309,167
10 transactions · 9 stateful · 2026-05-13 11:14:20 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,309,167 · 10 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x41be793a…9cc6
0x065c9d…c394
2 touches
0 conflicts
0x194f2c02…19e6
0x2a68ba…90c5
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x968bdacb…f461
0x2a68ba…90c5
2 touches
0 conflicts
0x0197c603…6bad
0x2ab50b…5c41
2 touches
0 conflicts
0x0849cefc…6a65
0x2ab50b…5c41
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity